# Review And Ship

ZoneGaze Flow keeps human review close to agent execution. Use it to inspect changes before committing, opening a pull request, or marking work done.

## Review The Task Output

Open the task card after the agent finishes or asks for review. Read the final response, warnings, terminal output, and changed-file summary.

Do not rely on the agent's final message alone. Verify the actual files and commands.

## Inspect Diffs

Use the task detail and Git views to inspect working-copy changes. Look for:

- files changed outside the task scope
- missing tests or validation
- generated files that do not match source changes
- private paths, tokens, or secrets
- formatting or build errors
- UI changes that need browser verification

![Git history and review surface](./assets/screenshots/web-git-history.png)

## Run Local Checks

Run the smallest check that proves the work, then broaden if the change is risky.

Examples:

```bash
npm run docs:check
npm run web:typecheck
npm run web:test
```

Use the project's own commands when they differ.

## Commit

Commit only after you have inspected the change and local validation is acceptable. Keep the commit message specific to the task.

## Pull Request

If your workflow uses pull requests, open a PR only after local validation. The PR should explain:

- what changed
- why it changed
- how it was verified
- any known limitations or skipped checks

## Done And Archive

Move the card to Done when the work is complete and reviewed. Archive cards that no longer need to stay in the active board.

![Archive view after work is moved out of active flow](./assets/screenshots/web-archive.png)

## Review Checklist

- Task scope matched the request.
- Diff contains no unrelated changes.
- Secrets and private paths are absent.
- Local validation ran or skipped checks are explained.
- Browser-visible changes were checked in a browser.
- Generated docs or assets were refreshed when needed.
- The card state matches the real Git state.
