4fac18c165
Sourced from https://github.com/tomasz-tomczyk/crit/tree/main/integrations/claude-code Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
122 lines
5 KiB
Markdown
122 lines
5 KiB
Markdown
---
|
|
description: "Review code changes or a plan with crit inline comments"
|
|
allowed-tools: Bash(crit:*), Bash(command ls:*), Read, Edit, Glob
|
|
---
|
|
|
|
# Review with Crit
|
|
|
|
Review and revise code changes or a plan using `crit` for inline comment review.
|
|
|
|
## Step 1: Determine review mode
|
|
|
|
Choose what to review based on context:
|
|
|
|
1. **User argument** - if the user provided `$ARGUMENTS` (e.g., `/crit my-plan.md`), review that file
|
|
2. **Recent plan** - if no argument, check if a plan was written earlier in this conversation. If so, review that file with `crit <plan-file>`
|
|
3. **Branch review** - otherwise, run `crit` with no arguments. It auto-detects what to review: uncommitted changes, or all changes on the current branch vs the default branch. Works on clean branches too.
|
|
|
|
Don't ask for confirmation — just proceed with whichever mode applies.
|
|
|
|
## Step 2: Launch crit and block until review completes
|
|
|
|
**CRITICAL — you MUST run this step. Do NOT skip it. Do NOT proceed without it.**
|
|
|
|
If a crit server is already running from earlier in this conversation, `crit` will automatically connect to it — no need to track ports or skip steps.
|
|
|
|
Run `crit` **in the background** using `run_in_background: true`:
|
|
|
|
```bash
|
|
# For a specific file:
|
|
crit <plan-file>
|
|
|
|
# For git mode (no args):
|
|
crit
|
|
```
|
|
|
|
This starts the daemon if needed (or connects to an existing one), opens the browser, and blocks until the user clicks "Finish Review". Feedback is printed to stdout when it exits.
|
|
|
|
Tell the user: **"Crit is open in your browser. Leave inline comments, then click Finish Review."**
|
|
|
|
**Do NOT proceed until `crit` completes.** Do NOT ask the user to type anything. Do NOT read `.crit.json` early. Wait for the background task to finish — that is how you know the human is done reviewing.
|
|
|
|
## Step 3: Read the review output
|
|
|
|
When `crit` completes, read the `.crit.json` file in the repo root (or working directory) using the Read tool.
|
|
|
|
The file contains structured JSON with comments per file:
|
|
|
|
```json
|
|
{
|
|
"files": {
|
|
"plan.md": {
|
|
"comments": [
|
|
{ "id": "c1", "start_line": 5, "end_line": 10, "body": "Clarify this step", "quote": "specific words", "resolved": false }
|
|
]
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
Identify all comments where `"resolved": false` or where the `resolved` field is missing (missing means unresolved). If a comment has a `"quote"` field, it contains the specific text the reviewer selected — focus your changes on the quoted text rather than the entire line range.
|
|
|
|
## Step 4: Address each review comment
|
|
|
|
For each unresolved comment:
|
|
|
|
1. Understand what the comment asks for (clarification, change, addition, removal)
|
|
2. If a comment contains a suggestion block, apply that specific change
|
|
3. Revise the **referenced file** to address the feedback - this could be the plan file or any code file from the git diff
|
|
4. Use the Edit tool to make targeted changes
|
|
5. Reply to the comment with what you did: `crit comment --reply-to <id> --resolve --author 'Claude Code' '<what you did>'`
|
|
|
|
When addressing multiple comments, use `--json` to resolve them all in one call:
|
|
|
|
```bash
|
|
echo '[
|
|
{"reply_to": "c1", "body": "Fixed", "resolve": true},
|
|
{"reply_to": "c2", "body": "Refactored as suggested", "resolve": true}
|
|
]' | crit comment --json --author 'Claude Code'
|
|
```
|
|
|
|
Editing the plan file triggers Crit's live reload - the user sees changes in the browser immediately.
|
|
|
|
**If there are zero review comments**: inform the user no changes were requested and stop the background `crit` process.
|
|
|
|
## Step 5: Signal completion and start next round
|
|
|
|
**CRITICAL — you MUST run this step. Do NOT skip it. Do NOT proceed without it.**
|
|
|
|
Run the **exact same `crit` command from Step 2** in the background using `run_in_background: true`. This is critical — if you launched `crit plan.md` in Step 2, you must run `crit plan.md` again here (not bare `crit`). The daemon is keyed by the arguments, so mismatched args will start a new daemon instead of reconnecting.
|
|
|
|
```bash
|
|
# Must match Step 2 exactly:
|
|
crit <same-args-as-step-2>
|
|
```
|
|
|
|
On subsequent calls, `crit` automatically signals round-complete first, then blocks again until the next "Finish Review" click.
|
|
|
|
Tell the user: **"Changes applied. Review the diff in your browser and click Finish Review when ready."**
|
|
|
|
**Do NOT proceed until `crit` completes.** When it does, go back to Step 3. If the user finishes with zero comments, the review is approved — stop the loop and proceed.
|
|
|
|
## Sharing
|
|
|
|
If the user asks for a URL, a link, to share the review, or to show a QR code, run:
|
|
|
|
```bash
|
|
crit share <file>
|
|
```
|
|
|
|
**Always relay the full output to the user** — copy the URL (and QR code if `--qr` was used) from the command output and include it directly in your response. Do not make them dig through tool output to find it.
|
|
|
|
To also show a QR code — **only in real terminal environments** with monospace font rendering (not mobile apps like Claude Code mobile, or web chat UIs where Unicode block characters won't render):
|
|
|
|
```bash
|
|
crit share --qr <file>
|
|
```
|
|
|
|
To remove a shared review:
|
|
|
|
```bash
|
|
crit unpublish
|
|
```
|