Reviewing Andy's work

When the Coding Agent finishes, you have two review surfaces — the walkthrough (before a PR is opened) and the pull/merge request (once it's open). This page covers what to look for and how to iterate at each step.

Before the PR: the walkthrough

After implementation finishes, Andy posts a walkthrough — a summary of the change for you to review before a PR exists. Open the task in the web app or the implementation-complete message in Slack to see:

Summary of changes — what the Coding Agent did, in plain language
Files changed — paths and a short diff per file
Test results — output from the test command, if tests ran
Caveats — things Andy wants you to look at, like a deferred follow-up or an assumption it made
Branch link — the actual branch on GitHub or GitLab, if you want to inspect it directly

This is your cheapest chance to course-correct. If something is off, click Make changes and describe what you want differently. The Coding Agent picks up from where it left off and pushes follow-up commits to the same branch.

If the walkthrough looks right, click Create pull request to open the PR.

Once the PR is open

Andy creates the PR/MR using the bot user (@meetandyai or the equivalent for your GitHub App install) and posts a link to it in the Slack thread. The task moves to PR open.

The PR description includes:

A summary of what the change does
A list of the main edits
A link back to the MeetAndy task page
Any caveats Andy wanted you to be aware of

From here it's a regular code review:

Read the diff on GitHub or GitLab as you would with any teammate's PR.
Run CI / preview deploys — Andy waits for these to settle before considering the task done.
Leave comments if you want changes.

Requesting changes after the PR opens

You have two ways to ask for changes once the PR is open:

PR comments on GitHub or GitLab — leave inline or general comments. Andy reads them and responds with follow-up commits to the same PR.
Reply in the Slack thread — describe what you want different. Andy treats this like a request-changes signal and pushes new commits.

If you've already moved on and want to take over manually, you can also just push to the branch yourself — the PR continues from your commits.

Approving and merging

Merging is manual. Andy never merges its own PRs — that's always your call. Use your usual GitHub/GitLab merge flow:

Approve the PR through your normal review process
Merge once CI is green and reviewers have signed off

When the PR merges, Andy automatically picks up the merge event and moves the task to Done. If you're using Jira, Andy can also update the linked ticket — see Reading and writing tickets.

What if you want to discard instead

If the work doesn't pan out and you don't want to merge:

Close the PR on GitHub / GitLab — Andy notices and moves the task to PR rejected
Click Discard and exit in the Slack thread or web app — Andy closes the PR (if open) and moves the task to Abandoned

Either way, the branch stays around in your Git host until you delete it manually — Andy doesn't clean up branches automatically.