comet-review

Review the implementation diff of the current Comet change without advancing its workflow.

2.9k|284|Updated May 14, 2026
One-click install
npx skills add https://github.com/rpamis/comet --skill comet-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comet-review
Source: https://github.com/rpamis/comet/tree/main/assets/skills/comet-review
Command: npx skills add https://github.com/rpamis/comet --skill comet-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When working on a Comet-managed change, you may want an independent, read-only code review of the current implementation diff without triggering phase transitions, verification runs, or state mutations. This Skill performs exactly that: a manual, phase-neutral review that reports concrete findings without modifying anything.

Core Features & Use Cases

  • Read-only diff review: Inspects the complete diff from a trusted baseline to the current worktree, including staged, unstaged, and untracked files, without writing, committing, or advancing the workflow.
  • Dual workflow support: Resolves review context for both Classic changes (proposal, design, tasks, specs, state queries) and Native changes (brief, acceptance items, verification evidence via comet native show).
  • Severity-ranked findings: Reports only concrete defects using CRITICAL, IMPORTANT, WARNING, and SUGGESTION severities, each tied to a file, line, and triggering scenario.
  • Use Case: Before running /comet-verify, ask for a manual review of your current change to catch logic defects, security risks, or missing test coverage early, while leaving the workflow state untouched.

Quick Start

Ask the assistant to run a manual read-only review of the current Comet change's implementation diff and list any findings by severity.

Frequently Asked Questions about comet-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manually review a Comet change without advancing the workflow?

Invoke the comet-review entry, which runs a read-only review of the current change's implementation diff. It never modifies files, commits, or transitions phases, and it does not replace Build or Verify validation.

What does the comet-review skill check in a code diff?

It checks implementation correctness, security and path-boundary risks, error handling, edge cases, omitted tasks, and test coverage. Findings are ranked as CRITICAL, IMPORTANT, WARNING, or SUGGESTION with file and line evidence.

Does comet-review work with both Classic and Native workflows?

Yes. For Classic it reads proposal, design, tasks, specs, and state queries; for Native it uses comet native show and comet native status to gather briefs, acceptance items, and verification evidence.

Can comet-review fix the issues it finds?

No. The review is strictly read-only and cannot modify files or state. If you ask to fix a finding, that becomes a separate write task handled through the repository's normal development workflow.

What happens if no baseline or change selection exists?

If selection is missing and multiple changes exist, it lists them and asks you to choose. If no trusted baseline can be established, it still reviews the visible worktree diff but labels the review scope as incomplete.