PR review
Capacitor’s review tools connect a pull request to the recorded sessions behind it. Use them alongside the diff to understand decisions, rejected approaches, and what verification actually ran.
Start a local review
Section titled “Start a local review”kcap review https://github.com/owner/repo/pull/123kcap review 'owner/repo#123'The command checks that review context exists on your Capacitor server, then launches Claude Code with a PR-scoped review MCP server. Claude must be installed and available on your path, and you must be signed in to Capacitor.
The parser also accepts GitLab merge-request URLs. Available context depends on the source-host integration and captured sessions.
If the command reports No review context found, confirm that sessions were recorded and linked to that PR. It does not launch a context-free review on a 404.
Ask about the implementation
Section titled “Ask about the implementation”Useful questions include:
- “Why did this change remove the cache invalidation?”
- “What alternatives were tried before this approach?”
- “Which tests actually ran, and did any failures remain?”
- “Was the original plan completed?”
- “Show me the session that changed this file.”
The six review tools are:
| Tool | Purpose |
|---|---|
get_pr_summary | Summarize sessions associated with the PR. |
list_pr_files | List changed files and related session context. |
get_file_context | Read the relevant context for a file. |
search_context | Search the linked session transcripts. |
list_sessions | List sessions linked to the PR. |
get_transcript | Read a paged session transcript. |
The tools return captured evidence. An absence of recorded test output is not proof that nobody ran a test outside the session.
Use review tools from an existing agent
Section titled “Use review tools from an existing agent”Setup registers the review MCP server for supported harnesses. Ask the agent to inspect a PR’s implementation context and supply the PR URL when the session is not already scoped to it.
This lets a hosted or local agent review the same evidence without starting a nested kcap review process. The local command above always launches Claude; the MCP evidence tools are usable by other supported agents.
Visibility
Section titled “Visibility”Review tools enforce session visibility and detail limits. Give a reviewer access through Visibility & sharing if they need to read a private implementation session.
A PR can include sessions from different harnesses. The reviewer does not need to use the harness that produced them.
Request an independent review loop
Section titled “Request an independent review loop”For an independent reviewer that returns findings and checks subsequent revisions, use Review flows. Those flows launch a separate participant on a connected daemon and maintain the rounds until the review concludes.
Session recap and recall searches past work beyond one PR.