Documentation

Reviewing file changes

Keep file destinations, contents and approvals understandable.

Before applying

Read the proposed file path and diff. Check created, modified and deleted status. Approving a file edit is separate from approving a command or additional network access.

Stale files

If the original file changes during review, the old review may no longer describe the operation. Refresh the proposal and review the current content. Keep important projects in version control or backed up.

After applying

Inspect the saved content and relevant validation result. Generated code may contain errors, missing imports or incomplete sections. A file being present alone does not prove it is complete.

Recovery

Use only recovery controls actually available for that operation. Rejected changes should stay unapplied. Do not assume a universal Undo exists for external command side effects.

Related guidance

Documentation hub → · Get help →