Comet Review
Manually review the implementation diff for the current Comet change. Report correctness, security, and edge-case issues without advancing the workflow.
Install
npx skills add rpamis/comet --skill comet-reviewgit clone --depth 1 https://github.com/rpamis/comet.git /tmp/comet
mkdir -p ~/.claude/skills
cp -r /tmp/comet/assets/skills/comet-review ~/.claude/skills/comet-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Comet Manual Code Review Perform one on-demand, read-only code review of the currently selected Comet change. This entry is not a workflow phase and does not replace Build or Verify checks and reviews. This entry is independent of `review_mode`. That field controls automatic reviews within the workflow; `/comet-review` is a single review explicitly requested by the user. Do not read, modify, or override the current change's `review_mode` during this invocation. ## Perform read-only operations The entire Skill invocation must remain read-only: - Do not modify, create, or delete files. - Do not stage, commit, switch branches, create branches, or create worktrees. - Do not run `comet state select`, `comet native select`, `comet state set`, `comet state transition`, phase guards, `comet native next`, or archive commands. - Do not fix findings, advance phase, or update tasks, state, verification reports, or review records. - Do not call this review a Verify pass or treat “no findings” as proof that tests passed. Only run commands needed to read files, query state, and inspect Git diffs. Checks that might execute project code, install dependencies, or produce files are outside this entry's scope. ## 1. Locate the project and current change 1. Use read-only Git queries to find the project root. Outside a Git repository, use the current Comet project root. 2. Run at the project root: ```bash comet status . --json ```
Details
- Skill name
comet-review- Repository
- rpamis/comet
- Path
assets/skills/comet-review/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Comet Review skill do?
Manually review the implementation diff for the current Comet change. Report correctness, security, and edge-case issues without advancing the workflow.
How do I install the Comet Review skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add rpamis/comet --skill comet-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Comet Review popular?
It lives in rpamis/comet, which has 3,306 GitHub stars and 317 forks.
Related skills
Brainstorming
3.3krpamis/comet
Transforms rough ideas into fully-formed designs. Structure your brainstorming sessions and develop ideas systematically.
Dispatching Parallel Agents
3.3krpamis/comet
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Finishing a Development Branch
3.3krpamis/comet
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Gha Security Review
1.2kgetsentry/skills
GitHub Actions security review for workflow exploitation vulnerabilities. Use when asked to "review GitHub Actions", "audit workflows", "check CI security", "GHA security", "workflow security review", or review .github/workflows/ for pwn requests, expression injection, credential theft, and supply chain attacks. Exploitation-focused with concrete PoC scenarios.
Find Bugs
1.2kgetsentry/skills
Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.
Security Model
1.2kgetsentry/skills
Define, review, or update SECURITY_MODEL.md files that tell security review tools a repository's threat model, trust boundaries, invariants, reportable finding classes, and exclusions. Use when asked to "write a security model", "threat model this repo for scanners", "define security review scope", "what counts as a vulnerability here", "update SECURITY_MODEL.md", "why did the scanner flag or miss this", or to check whether existing security guidance still matches the code. Not for running a security review or editing the SECURITY.md disclosure policy.
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.