Check a local folder before letting an AI tool edit

Local-folder execution uses the host tool and permissions. Prepare a project copy and a review boundary before giving a broad editing task.

Work through these checks

1. Path

confirm the exact selected directory. Record the evidence or the unresolved question before moving on.

2. Backup

retain a recoverable source version. Record the evidence or the unresolved question before moving on.

3. Tools

check required local dependencies. Record the evidence or the unresolved question before moving on.

4. Scope

state allowed changes and output paths. Record the evidence or the unresolved question before moving on.

5. Review

plan how to inspect the diff or changed files. Record the evidence or the unresolved question before moving on.

Put the checklist to work

For documentation cleanup, use a branch or copy and request a changed-file list with the proposed edits.

Keep the checklist beside the task brief and the actual output. Mark a check complete only after inspecting the relevant file, setting or event. If a required check cannot run in the current environment, describe that gap and choose an appropriate next review rather than substituting a confident summary.

A boundary to remember

A narrow brief is useful guidance, but it is not an operating-system permission boundary.

For the corresponding controls and troubleshooting steps, read the desktop help guide. These checks are a practical review aid; adapt them to the specific source material and intended use of your deliverable.