Review and source changes

Review the working files as well as the agent's explanation. An agent may complete its requested edit while leaving a failing check, an unexpected file, or an untested behavior.

1. Read the summary and compare it with the requested scope.
2. Open the diff and inspect every changed file.
3. Check the reported commands and their results.
4. Exercise the changed behavior where a test cannot establish the result.
5. Ask for corrections or explicitly authorize the next Git action.

For a UI change, inspect the page at the sizes affected. For a bug fix, look for evidence that the reproduction now behaves correctly. A passing build does not prove either result.

The diff viewer includes unpublished local edits. For a workspace linked to a pull request, sidebar additions and deletions come from GitHub's PR state and can differ from the local diff.

GitHub actions need GitHub access on the host. Be explicit about whether you want a commit, push, pull request, or merge. These are separate outcomes. After creating a PR, check its actual status and checks; do not infer that it merged from an agent's plan to merge it.

Next: Workspaces and worktrees.