SKILL·E305F5

crit-cli

Name: crit-cli
Author: tomasz-tomczyk

tomasz-tomczyk

Updated Yesterday

866

Metaautomation

About

The crit-cli skill enables programmatic creation and management of code review comments through CLI commands, supporting multi-agent workflows on shared artifacts. It allows publishing/unpublishing reviews, syncing with GitHub PRs, and reading/writing crit JSON files. Use this for automated review operations, not for interactive review sessions which require the separate `crit` skill.

Quick Install

Claude Code

Recommended

Primary

npx skills add tomasz-tomczyk/crit -a claude-code

Plugin CommandAlternative

/plugin add https://github.com/tomasz-tomczyk/crit

Git CloneAlternative

git clone https://github.com/tomasz-tomczyk/crit.git ~/.claude/skills/crit-cli

Copy and paste this command in Claude Code to install this skill

Documentation

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.

Comments have three scopes:

Line comments (scope: "line") — tied to specific lines, stored in files.<path>.comments
File comments (scope: "file") — about a file overall, stored in files.<path>.comments with start_line: 0
Review comments (scope: "review") — general feedback, stored in the top-level review_comments array

The review file path is shown by crit status.

Reading comments

When crit completes a review round, read stdout and follow its instructions. Unresolved comments are often embedded in that prompt as JSON. Check stderr for approved: true or approved: false.

When you need to read comments separately:

crit comments            # human-readable, unresolved only (default)
crit comments --json     # flat JSON for agents
crit comments --all      # include resolved comments
crit comments --plan <slug>   # plan reviews
crit comments [path]     # explicit review.json or .crit directory

Review-level comments are listed first — easy to miss in raw review.json. Uses the same review resolution as crit comment (--output, --plan, daemon session).

Multiple active sessions

When more than one review session matches the current directory and branch, crit comment refuses to guess. Run crit status (or crit status --json) to list every active session, then target the intended review explicitly:

crit comment --session <id> --author <name> <path>:<line> <body>
crit comment --session <id> --json --file comments.json --author <name>

The JSON status output exposes the candidates in sessions.

Review file format

{
  "review_comments": [
    {
      "id": "r_f1e2d3",
      "body": "Overall the architecture looks good",
      "scope": "review",
      "author": "User Name",
      "resolved": false,
      "replies": [
        { "id": "rp_b4a5c6", "body": "Thanks, addressed the minor issues", "author": "Copilot" }
      ]
    }
  ],
  "files": {
    "path/to/file.go": {
      "comments": [
        {
          "id": "c_a1b2c3",
          "start_line": 5,
          "end_line": 10,
          "body": "Comment text",
          "quote": "the specific words selected",
          "anchor": "The sessions table needs a complete rewrite...",
          "author": "User Name",
          "resolved": false,
          "replies": [
            { "id": "rp_c7d8e9", "body": "Fixed by extracting to helper", "author": "Copilot" }
          ]
        }
      ]
    }
  }
}

Field rules:

resolved: false or missing — both mean unresolved. Only true means resolved.
quote (optional): the specific text the reviewer selected — narrows scope within the line range. Focus changes on the quoted text rather than the entire range.
anchor (line comments): full text of the commented lines when placed. When edits shift line numbers, locate content by anchor rather than trusting start_line/end_line.
drifted: true: original content was removed or heavily rewritten — line numbers are approximate at best.
Unresolved comments may have replies — read them before acting.

Authoring and replying with `crit comment`

# Review-level (general feedback)
crit comment --author 'Copilot' '<body>'

# File-level (whole file, no line numbers)
crit comment --author 'Copilot' <path> '<body>'

# Line (single line or range)
crit comment --author 'Copilot' <path>:<line> '<body>'
crit comment --author 'Copilot' <path>:<start>-<end> '<body>'

# Reply to an existing comment
crit comment --reply-to <id> --author 'Copilot' '<body>'

Hard rules:

Always pass --author 'Copilot' (or your agent name) so comments are attributed correctly.
Always single-quote the body — double quotes break on backticks and shell metachars.
Line numbers reference the file on disk (1-indexed), not diff line numbers.
Reply bodies support markdown — use code fences and inline code where helpful.
Only pass --resolve when the user explicitly asks. Never resolve proactively.

Bulk commenting with `--json`

When leaving 3+ comments, use --json for atomicity (single write, no partial state) and speed (one process). The JSON payload can come from stdin or from --file <path>:

# Stdin is fine when bodies are short single lines:
echo '[
  {"body": "overall feedback", "scope": "review"},
  {"path": "session.go", "body": "restructure", "scope": "file"},
  {"file": "src/auth.go", "line": 42, "body": "Missing null check"},
  {"file": "src/auth.go", "line": "50-55", "body": "Extract to helper"},
  {"reply_to": "c_a1b2c3", "body": "Fixed — added null check"},
  {"reply_to": "r_f1e2d3", "body": "Done"}
]' | crit comment --json --author 'GitHub Copilot'

For multi-paragraph bodies, prefer --file. A raw newline inside a "body" string is invalid JSON, and it's easy to introduce one when shell-quoting a heredoc. Write the JSON to a temp file via your edit tool, then:

crit comment --json --file /tmp/crit-bulk.json --author 'GitHub Copilot'

--file - is shorthand for stdin if you need to be explicit.

Per-entry schema:

Field	Type	Required	Notes
`file` / `path`	string	line/file comments	Relative path. `path` alone (no `line`) → file-level.
`line`	int/string	line comments	`42` or `"45-47"`
`end_line`	int	optional	Defaults to `line`
`body`	string	always
`author`	string	optional	Per-entry override; falls back to `--author`
`scope`	string	optional	`"review"` / `"file"` — usually inferred
`reply_to`	string	replies	Comment ID (`c_…` or `r_…`)
`resolve`	bool	optional	Only when user explicitly asks

Scope inference (when scope omitted): has reply_to → reply; no file/path and no line → review-level; path but no line → file-level; file/path + line → line.

Multi-file disambiguation

If crit comment errors with "comment found in multiple files", IDs collided across files. Disambiguate with --path:

crit comment --reply-to c_a1b2c3 --path src/auth.go --author 'Copilot' 'Fixed the null check'

In --json mode, set the file field on the entry. Review-level IDs (r_…) are globally unique and never need this.

Plan-mode comments

Plan reviews (via crit plan or the ExitPlanMode hook) store the review file in ~/.crit/plans/<slug>/. Always pass --plan <slug> — without it, crit comment looks in the project root and won't find the comments. The slug is shown in the review feedback prompt.

crit comment --plan my-plan-2026-03-23 --reply-to c_a1b2c3 --author 'Copilot' 'Updated the plan'

GitHub PR sync

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

Requires gh CLI installed and authenticated. PR number is auto-detected from the current branch.

--event values: comment (default), approve, request-changes. -m adds a review-level body message.

Sharing

crit share <file> [file...]                          # Upload and print URL
crit share --qr <file>                               # Also print QR code (terminal only)
crit share --org <slug> <file>                       # Share under an organization
crit share --org <slug> --visibility unlisted <file> # Org share with explicit visibility
crit unpublish [file...]                              # Remove shared review

Always relay the output — copy the URL (and QR if used) into your response. Don't make the user dig through tool output.
--qr is terminal-only — skip in mobile apps, web chat UIs, or anywhere Unicode block characters won't render correctly.
--org <slug> shares under an organization. Visibility defaults to organization (members only). Override with --visibility (organization, unlisted, public).
Unpublish uses the persisted delete token in the review file — no extra args needed.

GitHub Repository

tomasz-tomczyk/crit

Path: integrations/github-copilot/skills/crit-cli

agentic-codingai-agentsai-toolsclicode-reviewdeveloper-tools

FAQ

Frequently asked questions

What is the crit-cli skill?

crit-cli is a Claude Skill by tomasz-tomczyk. Skills package instructions and resources that Claude loads on demand, so Claude can perform crit-cli-related tasks without extra prompting.

How do I install crit-cli?

Use the install commands on this page: add crit-cli to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.

What category does crit-cli belong to?

crit-cli is in the Meta category, tagged automation.

Is crit-cli free to use?

Yes. crit-cli is listed on AIMCP and free to install.

Related Skills

content-collections

Meta

This skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.

View skill

polymarket

Meta

This skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.

View skill

creating-opencode-plugins

Meta

This skill helps developers create OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It provides the plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript modules. Use it when you need to intercept, monitor, or extend the OpenCode AI assistant's lifecycle with custom event-driven logic.

View skill

sglang

Meta

SGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.

View skill

crit-cli

About

Quick Install

Claude Code

Documentation

Crit CLI Reference

Reading comments

Multiple active sessions

Review file format

Authoring and replying with crit comment

Bulk commenting with --json

Multi-file disambiguation

Plan-mode comments

GitHub PR sync

Sharing

GitHub Repository

Frequently asked questions

What is the crit-cli skill?

How do I install crit-cli?

What category does crit-cli belong to?

Is crit-cli free to use?

Related Skills

Authoring and replying with `crit comment`

Bulk commenting with `--json`