Files and folders

Inspect before changing

Ask the assistant to list a selected project, find a relevant file and read the exact portion needed.

Start with read-only work so you can verify the chosen workspace and expected paths.

Sensitive-file reads can be blocked by Rigbolt policy. Never ask to dump credentials or hidden secrets.

Make a controlled edit

Describe the file and expected result precisely.

Use Rigbolt file patch/write tools to make the smallest justified change.

Inspect the diff, then run the project's tests or typecheck in the terminal.

Review Live Sessions and Code Review for observable results.

If an edit fails

Verify the workspace scope, file path and whether the file was changed by another process.

For stale-patch errors, re-read the latest file and prepare a fresh patch rather than forcing an overwrite.

For denied files, check policy and path permissions; do not attempt to bypass secret protections.