GitHub Review Iteration
prisma/orm
Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.
Spawn a reviewer sub-agent to assess a change set against habit-hooks's coding principles.
Install Habit Hooks Review
$ npx skills add habit-hooks/habit-hooks --skill habit-hooks-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install habit-hooks/habit-hooks habit-hooks-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/habit-hooks/habit-hooks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/habit-hooks-review .claude/skills/habit-hooks-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "habit-hooks-review" agent skill from https://github.com/habit-hooks/habit-hooks/tree/main/skills/habit-hooks-review into .claude/skills/habit-hooks-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "habit-hooks-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/habit-hooks/habit-hooks/tree/main/skills/habit-hooks-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add habit-hooks/habit-hooks --skill habit-hooks-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install habit-hooks/habit-hooks habit-hooks-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/habit-hooks/habit-hooks.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/habit-hooks-review .agents/skills/habit-hooks-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "habit-hooks-review" agent skill from https://github.com/habit-hooks/habit-hooks/tree/main/skills/habit-hooks-review into .agents/skills/habit-hooks-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "habit-hooks-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add habit-hooks/habit-hooks --skill habit-hooks-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install habit-hooks/habit-hooks habit-hooks-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/habit-hooks/habit-hooks.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/habit-hooks-review .cursor/skills/habit-hooks-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "habit-hooks-review" agent skill from https://github.com/habit-hooks/habit-hooks/tree/main/skills/habit-hooks-review into .cursor/skills/habit-hooks-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "habit-hooks-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/habit-hooks/habit-hooks.git --path skills/habit-hooks-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add habit-hooks/habit-hooks --skill habit-hooks-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install habit-hooks/habit-hooks habit-hooks-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/habit-hooks/habit-hooks.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/habit-hooks-review .gemini/skills/habit-hooks-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "habit-hooks-review" agent skill from https://github.com/habit-hooks/habit-hooks/tree/main/skills/habit-hooks-review into .gemini/skills/habit-hooks-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "habit-hooks-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install habit-hooks/habit-hooks habit-hooks-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add habit-hooks/habit-hooks --skill habit-hooks-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/habit-hooks/habit-hooks.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/habit-hooks-review .github/skills/habit-hooks-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "habit-hooks-review" agent skill from https://github.com/habit-hooks/habit-hooks/tree/main/skills/habit-hooks-review into .github/skills/habit-hooks-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "habit-hooks-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add habit-hooks/habit-hooks --skill habit-hooks-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install habit-hooks/habit-hooks habit-hooks-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/habit-hooks/habit-hooks.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/habit-hooks-review .opencode/skills/habit-hooks-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "habit-hooks-review" agent skill from https://github.com/habit-hooks/habit-hooks/tree/main/skills/habit-hooks-review into .opencode/skills/habit-hooks-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "habit-hooks-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
habit-hooks-review- GitHub stars
- 222
- Token cost
- ~1.5k tokens
- SKILL.md length
- 764 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Spawn a reviewer sub-agent to assess a change set against habit-hooks's coding principles.
- Tasks that involve Subagents
- SKILL.md covers How to invoke, The brief, After the reviewer returns and Why this is a separate skill…
- Calls pnpm and npm
What it does
Habit Hooks Review is an agent skill from habit-hooks/habit-hooks. Spawn a reviewer sub-agent to assess a change set against habit-hooks's coding principles. Use AFTER habit-hooks reports clean — habit-hooks catches structural smells; this catches what it cannot (correctness, tests, design, missed edge cases).
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Subagents. The repository describes itself as: Automated quality checks that nudge AI coding agents toward better habits. The licence is MIT.
When your agent uses it
- Tasks that involve Subagents
Example prompts
- “/habit-hooks-review”
What it can do on your machine
Read from SKILL.md and the folder at commit 5603331. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpmnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm and npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Habit Hooks Review loads about 1.5k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 764 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from habit-hooks/habit-hooks at commit 5603331, republished under its MIT licence (© habit-hooks). 764 words, ~1,512 tokens.
Download SKILL.mdSave it as
.claude/skills/habit-hooks-review/SKILL.md (or your agent's skills folder).- name
- habit-hooks-review
- description
- Spawn a reviewer sub-agent to assess a change set against habit-hooks's coding principles. Use AFTER habit-hooks reports clean — habit-hooks catches structural smells; this catches what it cannot (correctness, tests, design, missed edge cases).
Habit Hooks Review
You are reading this because habit-hooks reported clean and you (the implementing agent) need a second pair of eyes on the change set before declaring the work done.
A green habit-hooks run is necessary, not sufficient. habit-hooks catches structural smells — oversized functions, high complexity, any, dead bindings, stale TODOs, comments standing in for unclear code. It cannot see:
- Correctness bugs (logic errors, off-by-one, wrong branch taken).
- Design issues (wrong abstraction, leaky boundaries, missing seam).
- Test coverage gaps (a happy path test masquerading as full coverage, untested error paths).
- Missed edge cases (empty input, concurrent calls, mid-iteration mutation).
- Naming clarity (a name that reads fine in isolation but is wrong for the role it plays).
- Missing abstractions that do not trip a threshold (two functions that should share a type, three call sites that should share a helper).
This skill spawns a reviewer sub-agent to look for exactly those things.
How to invoke
Use the Task tool to spawn a general-purpose sub-agent with the brief below. Do not review the change yourself first — the value of this skill is the fresh read. Include the diff scope (commit range, branch, or staged files) in the brief so the reviewer knows what to look at.
The brief
Paste this verbatim into the Task tool's prompt, filling in the change-set scope at the top:
You are reviewing a change set against the principles below. The implementing agent has already run habit-hooks and it reports clean — so structural smells (function size, parameter count, complexity, file length, any, unused vars, etc.) are already covered. Do not re-flag anything habit-hooks catches. Focus on what habit-hooks cannot see.
Change set under review: <describe scope: commit range, branch diff, or staged files>
Ground rules:
- PASS-when-clean is the right answer. Do not manufacture issues to look thorough.
- If the change is small and well-shaped, say so. A two-line PASS is a valid outcome.
- Cite
file:linefor every finding. No vague "consider revisiting the design" — point at something. - Assume the change was written TDD-first. If tests are missing or asymmetric (only happy paths, only the new code), say so.
Principles to review against:
- KISS — is there a simpler approach that does the same job?
- Single responsibility — does each new function/class have one reason to change?
- Naming clarity — does every name reveal intent? Can a future reader understand it in five seconds?
- Readability — is the change comfortable to navigate, or does it ask the reader to hold too many ideas?
- No shortcuts — flag
eslint-disable,@ts-ignore,as any, swallowed catches, magic numbers without context. Even if the linter is happy, those are debts. - Correctness — read the logic, not just the shape. Look for off-by-one, wrong-branch, swallowed errors, race conditions, mid-iteration mutation.
- Edge cases — empty input, single-element input, max/min, error paths.
- Test coverage — is each new behaviour exercised? Are failure modes tested, not just happy paths?
Show full SKILL.md (289 more words)Show less
Categorise findings:
- Blocking — must be fixed before merge. Correctness bugs, broken tests, gate failures, missing test for new behaviour.
- Worth flagging — design or clarity issues the author should weigh. Not necessarily blocking, but worth a conversation.
- Nits — small polish items. Hard cap: two. If you have more than two nits, drop the weakest ones.
Confirm the gate:
Run (or read the most recent output of) all four scripts: typecheck, lint, test, build. Detect the package manager from the lockfile in the project root (pnpm-lock.yaml → pnpm, yarn.lock → yarn, bun.lock or bun.lockb → bun, otherwise npm) and invoke accordingly — pnpm/yarn/bun take the script name directly (pnpm typecheck), npm needs run (npm run typecheck).
All four must exit 0. Report each exit code in the output.
Output format (return this verbatim):
## Verdict
<PASS | CHANGES NEEDED>
## Findings
### Blocking
- <file:line — one-line summary. One short paragraph of detail.>
- (or: "None.")
### Worth flagging
- <file:line — one-line summary. One short paragraph of detail.>
- (or: "None.")
### Nits (max 2)
- <file:line — one-line summary.>
- (or: "None.")
## Gate output
- typecheck: exit <code>
- lint: exit <code>
- test: exit <code>
- build: exit <code>
## Specific calls
<Anything that does not fit the categories above — design questions for the author, a follow-up worth scheduling, a pattern worth a CLAUDE.md note. Keep it short or omit the section entirely.>After the reviewer returns
- If PASS: relay the verdict and finish the task.
- If CHANGES NEEDED: do not silently fix everything. Surface the findings to the user, agree which to act on, and only then implement. Blocking items must be resolved; worth-flagging items are a conversation, not an assignment.
Why this is a separate skill from code-style-review
code-style-review is invoked by a human, on a file or a region, to start a discussion before refactoring. It lists problems for the human to triage and prioritise.
habit-hooks-review is invoked by an agent, after a clean automated gate, to get a second-pass quality read on a finished change set. The shape of the output is different — verdict-driven, scoped to the diff, framed for an agent that is about to declare done.
The two skills are complementary, not interchangeable. Do not use code-style-review as a stand-in here: it will not check the gate, will not categorise by blocking severity, and will not return a verdict.
© habit-hooks, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/habit-hooks-review of habit-hooks/habit-hooks.
Open the folder on GitHubat commit 5603331
Compare with similar skills
Habit Hooks Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Habit Hooks Review this skillhabit-hooks/habit-hooks | 222 | — | ~1.5k | Automated safety check: Pass | MIT | |
| GitHub Review Iterationprisma/orm | 48k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Cherry Studio PR ReviewCherryHQ/cherry-studio | 53k | — | ~3.9k | Automated safety check: Pass | AGPL-3.0 | |
| Jevgrepdzhng/jevgrep | 2.5k | — | ~741 | Automated safety check: Pass | MIT | |
| PR Cyclejaemk/cached | 2.1k | — | ~4.8k | Automated safety check: Notes | MIT | |
| PR Reviewjaemk/self_update | 961 | — | ~1.5k | Automated safety check: Notes | MIT |
Similar skills
- Official
Cherry Studio PR Review
CherryHQ/cherry-studio
Reviews Cherry Studio branches, pull requests, commits, files and docs against the project's own architecture, naming, API-boundary and UI rules, report-only by default.
Jevgrep
dzhng/jevgrep
A skill your agent uses for questions about how, why, or where behavior works in a repository, including questions that name a function or setting.
PR Cycle
jaemk/cached
PR review-and-update cycle — the orchestrator that takes a PR from review to resolved.
PR Review
jaemk/self_update
Targeted, read-only review of a PR or checked-out branch. An agent skill from jaemk/self_update.
Cursor Composer Task Delegate
Chachamaru127/claude-code-harness
Hands one implementation task to Cursor Composer in an isolated git worktree, then reviews its diff and cherry-picks the result into the main branch.
More from habit-hooks/habit-hooks
Release Habit Hooks
habit-hooks/habit-hooks
Cut a new release of the habit-hooks packages. An agent skill from habit-hooks/habit-hooks.
Habit Hooks Prompting
habit-hooks/habit-hooks
Write or revise a habit-hooks coaching prompt. An agent skill from habit-hooks/habit-hooks.
Writing Docs
habit-hooks/habit-hooks
Write or trim habit-hooks documentation under docs/. An agent skill from habit-hooks/habit-hooks.
Related
Categories
Questions about Habit Hooks Review
What does Habit Hooks Review do?
Spawn a reviewer sub-agent to assess a change set against habit-hooks's coding principles. Habit Hooks Review is an agent skill from habit-hooks/habit-hooks. Spawn a reviewer sub-agent to assess a change set against habit-hooks's coding principles.
When should I use Habit Hooks Review?
Habit Hooks Review fits situations like: tasks that involve Subagents.
How do I install Habit Hooks Review in Claude Code?
Run `npx skills add habit-hooks/habit-hooks --skill habit-hooks-review -a claude-code`. Or copy the skill folder (skills/habit-hooks-review in habit-hooks/habit-hooks) into .claude/skills/habit-hooks-review in your project. Claude Code loads it when a task matches its description.
How do I install Habit Hooks Review in Codex?
Run `npx skills add habit-hooks/habit-hooks --skill habit-hooks-review -a codex`. Or copy the skill folder (skills/habit-hooks-review in habit-hooks/habit-hooks) into .agents/skills/habit-hooks-review in your project. Codex loads it when a task matches its description.
Can I use Habit Hooks Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add habit-hooks/habit-hooks --skill habit-hooks-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/habit-hooks-review, .gemini/skills/habit-hooks-review, .github/skills/habit-hooks-review and .opencode/skills/habit-hooks-review in your project.
What does Habit Hooks Review need to run?
Going by SKILL.md and its folder, Habit Hooks Review needs the command-line tools its instructions call (pnpm and npm).
Does Habit Hooks Review access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Habit Hooks Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Habit Hooks Review use?
Habit Hooks Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Habit Hooks Review use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Habit Hooks Review?
Skills that share tags, products or a category with Habit Hooks Review: GitHub Review Iteration (prisma/orm, 48k stars), Cherry Studio PR Review (CherryHQ/cherry-studio, 53k stars), Jevgrep (dzhng/jevgrep, 2.5k stars) and PR Cycle (jaemk/cached, 2.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Habit Hooks Review?
habit-hooks (a GitHub organization) maintains it in habit-hooks/habit-hooks, which has 222 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 2, 2026.
Source: habit-hooks/habit-hooks on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.