Workflow guide / 01

Don’t just ask for
an edit. Check it.

A useful AI edit has two obligations: change the right thing and show that the intended file changed. Ganado Bridge’s file tools are designed to keep those steps distinct.

1. Start from the real file

Ask the assistant to identify the exact path and read the current contents. Avoid asking it to patch from a remembered snippet or an earlier upload. Read pages until the relevant context is available. A full read provides the SHA-256 value used for a later checked write.

2. State the smallest intended change

A precise request names the file, the desired result, what should remain untouched and how success will be checked. For example: “In this config, change only the local development port. Leave production values unchanged. Read the file back and run its existing validation.”

3. Compare before changing

The write or edit call supplies the expected current hash. If another program has changed the file, Bridge rejects the stale update. The assistant should re-read and reconsider the change, not blindly retry with a new hash. A literal edit must find exactly one occurrence; zero or multiple matches require a more specific replacement.

4. Read back, then test

A successful write receipt proves a file operation completed, not that the application works. Read back the changed section, inspect the diff where available and run the project’s appropriate checks. Keep the command result separate from the model’s interpretation.

What this does not protect against

Hash comparison is a concurrency check, not a sandbox or a guarantee of correctness. An authorized terminal command can bypass the file-edit workflow and modify the same file directly. The agent also runs with the OS user’s existing access. Keep backups and use the narrowest practical account for sensitive work.

A prompt you can adapt

Read the current file at the path I provide.
Describe the minimal intended change.
Use a checked edit; do not overwrite a changed file.
Read back the result and run the existing validation.
Report the changed path and actual validation result.

Use this only after connecting an authorized machine. The website preview itself does not execute these steps.

Try the local evaluation →