Ullrich Schäfer 4fac18c165

Add crit command and skill for inline code review

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>

2026-03-22 12:31:08 +01:00

6.7 KiB

Raw Blame History

name	description
crit-cli	Use when working with crit CLI commands, .crit.json files, addressing review comments, leaving inline code review comments, sharing reviews via crit share/unpublish, pushing reviews to GitHub PRs, or pulling PR comments locally. Covers crit comment, crit share, crit unpublish, crit pull, crit push, .crit.json format, and resolution workflow.

Crit CLI Reference

If a plan was just written and the user said /crit or crit, invoke the /crit command — do not use this reference skill. This skill covers CLI operations like crit comment, crit pull/push, and crit share.

.crit.json Format

After a crit review session, comments are in .crit.json. Comments are grouped per file with start_line/end_line referencing the source:

{
  "files": {
    "path/to/file.md": {
      "comments": [
        {
          "id": "c1",
          "start_line": 5,
          "end_line": 10,
          "body": "Comment text",
          "quote": "the specific words selected",
          "author": "User Name",
          "resolved": false,
          "replies": [
            { "id": "c1-r1", "body": "Fixed by extracting to helper", "author": "Claude" }
          ]
        }
      ]
    }
  }
}

Reading comments

Comments are grouped per file with start_line/end_line referencing source lines in that file
quote (optional): the specific text the reviewer selected — narrows the comment's scope within the line range. When present, focus your changes on the quoted text rather than the entire line range
resolved: false or missing — both mean unresolved. Only true means resolved.
Address each unresolved comment by editing the relevant file at the referenced location

Resolving comments

After addressing a comment, reply to it using the CLI:

crit comment --reply-to c1 --resolve --author 'Claude Code' 'Fixed by extracting to helper'

This adds a reply to the comment thread and marks it resolved. You can also reply without resolving (omit --resolve) if discussion is ongoing.

Leaving Comments with crit comment CLI

Use crit comment to add inline review comments to .crit.json programmatically — no browser needed:

# Single line comment
crit comment --author 'Claude Code' <path>:<line> '<body>'

# Multi-line comment (range)
crit comment --author 'Claude Code' <path>:<start>-<end> '<body>'

# Reply to an existing comment (with optional --resolve)
crit comment --reply-to <id> --author 'Claude Code' '<body>'
crit comment --reply-to <id> --resolve --author 'Claude Code' '<body>'

Examples:

crit comment --author 'Claude Code' src/auth.go:42 'Missing null check on user.session — will panic if session expired'
crit comment --author 'Claude Code' src/handler.go:15-28 'This error is swallowed silently'
crit comment --reply-to c1 --resolve --author 'Claude Code' 'Added null check on line 42'

Rules:

Always use --author 'Claude' (or your agent name) so comments are attributed correctly
Always use single quotes for the body — double quotes will break on backticks and special characters
Paths are relative to the current working directory
Line numbers reference the file as it exists on disk (1-indexed), not diff line numbers
Comments are appended — calling crit comment multiple times adds to the list, never replaces
No setup needed — crit comment creates .crit.json automatically if it doesn't exist
Do NOT run crit after leaving comments — that triggers a new review round

Bulk commenting (recommended for multiple comments)

When leaving 3+ comments, use --json to add them all in one atomic operation:

echo '[
  {"file": "src/auth.go", "line": 42, "body": "Missing null check"},
  {"file": "src/auth.go", "line": 50, "end_line": 55, "body": "Extract to helper"},
  {"file": "src/handler.go", "line": 10, "body": "Swallowed error"}
]' | crit comment --json --author 'Claude Code'

Replies and resolves work too:

echo '[
  {"reply_to": "c1", "body": "Fixed — added null check", "resolve": true},
  {"reply_to": "c2", "body": "Extracted to validateSession()"}
]' | crit comment --json --author 'Claude Code'

JSON schema per entry:

Field	Type	Required	Description
`file`	string	yes (new comment)	Relative file path
`line`	int	yes (new comment)	Start line (1-indexed)
`end_line`	int	no	End line (defaults to `line`)
`body`	string	yes	Comment text
`author`	string	no	Per-entry override (falls back to `--author`)
`reply_to`	string	yes (reply)	Comment ID to reply to (e.g. `"c1"`)
`resolve`	bool	no	Mark the parent comment resolved

Benefits over individual crit comment calls:

Atomic — one write to .crit.json, no partial state
Faster — single process invocation instead of N
Safer — no race conditions with concurrent crit processes

GitHub PR Integration

crit pull [pr-number]                                    # Fetch PR review comments into .crit.json
crit push [--dry-run] [--event <type>] [-m <msg>] [pr]  # Post .crit.json comments as a GitHub PR review

Requires gh CLI installed and authenticated. PR number is auto-detected from the current branch, or pass it explicitly.

Event types for --event: comment (default), approve, request-changes. Use -m to add a review-level body message.

If the user asks for a URL, a link, to share their review, or to show a QR code, use crit share:

crit share <file> [file...]   # Upload and print URL
crit share --qr <file>        # Also print QR code (terminal only)
crit unpublish                # Remove shared review