Review the PR and improve the process

Shaka produces a pull request with an evidence packet: an explanation of the change, checks and review results, visual comparisons when relevant, and what remains unverified.

Use that record to decide what happens next. Keep it for regular retrospectives that improve future work, including automatic merges.

Find what needs your attention

Start near the top of the PR description:

Look for	What it tells you
Summary and Intent	What changed, why, and whether it matches your request.
Verification	What was checked and what remains unproven.
Decisions to make, when present	Questions needing your judgment, with options and a recommendation.
Checkpoint link	The assessment of whether the result is worth merging, including unresolved concerns.

Check whether human review is needed. Inspect screenshots or try the changed feature when your judgment depends on the result. Open Code Review or Code Walkthrough for closer examination.

Evidence should cover the version you're reviewing. Passing checks support a decision; they do not settle every product choice or prove every claim.

Walk through the code together

Ask for an interactive tour when you want to understand a PR before deciding:

$shaka Walk me through https://github.com/OWNER/REPO/pull/123 one concept at a time.

The agent starts with a short agenda, explains one concept, and pauses for your questions. Say next to continue, or ask to change the depth, revisit a concept, or skip ahead. Larger PRs get a lightweight coverage map that connects concepts to changed files and tracks what has been covered.

The tour follows a specific revision and refreshes when the comparison changes. It complements the published Code Walkthrough and selective notes on the diff. Finishing the tour does not approve or authorize merging the PR.

Give feedback or merge

Explain the result you want in the owning chat. If you comment on GitHub, paste the comment link into that chat.

Under Ask, tell the agent when you're ready:

You can merge.

You can also merge through GitHub. Confirm that its commit is the version you reviewed. Required checks and approvals still apply.

Under Auto, the agent merges when the change is ready.

Improve the process over time

Regularly ask your agent to examine completed PRs and what happened after merging. Look for patterns in correctness, review rounds, repeated repairs, token use, and timing.

Skills such as AI Hero's /retro and Poteto's /reflect can help turn those lessons into improvements.

For lookup, see PR record details, usage and cost, and feedback and recovery.