Best use case
review is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Deep code review of recent changes or specified files
Teams using review should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/review/SKILL.md --create-dirs "https://raw.githubusercontent.com/hivellm/rulebook/main/.claude/skills/review/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/review/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How review Compares
| Feature / Agent | review | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Deep code review of recent changes or specified files
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
Perform a thorough code review. If $ARGUMENTS is provided, review those specific files or the given PR/commit. Otherwise, review uncommitted changes via `git diff`. Steps: 1. Get the diff (git diff or specified files) 2. Review for correctness, bugs, and edge cases 3. Check adherence to project patterns and conventions 4. Identify security concerns 5. Report findings as: blocker / suggestion / nit with file:line references
Related Skills
We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.