A structured code-review command that examines selected files, recent changes, or a pull request, sometimes using specialized reviewers for different file types.

Use it to review staged or unstaged changes, a directory, or a pull request. It also supports focused security and performance reviews.

It gathers the relevant change history and checks code from several angles, helping reveal security, performance, design, accessibility, and testing problems.

How bugrabilge/bilge-development-kit configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to bugrabilge/bilge-development-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/bugrabilge/bilge-development-kit/main/.claude/skills/review/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/bugrabilge/bilge-development-kit

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/review/github.svg)](https://agentmods.dev/skills/bugrabilge/bilge-development-kit/review)

Your own site

<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/review"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/review/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/review"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 838 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00043	$0.00838
Opus 5.5	$0.00017	$0.00335
Sonnet 5.5	$0.00009	$0.00168
Haiku 4.5	$0.00004	$0.00084

Measured 2mo ago against content hash 5df2d4b03bec, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/review/SKILL.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/review - Code Review

$ARGUMENTS

Purpose

This command performs a structured code review on specified files, directories, or recent changes.

Sub-commands

/review                - Review all staged/unstaged changes
/review [file/dir]     - Review specific file or directory
/review pr             - Review current PR changes
/review security       - Security-focused review
/review performance    - Performance-focused review

Behavior

When /review is triggered:

Identify scope
- What files/changes to review
- Auto-collect context using tools:
  1. Run git branch --show-current
  2. Run git diff --cached --stat
  3. Run git diff --stat
  4. Run git log --oneline -5

Multi-agent analysis Invoke relevant agents based on file types:

File Pattern	Agent	Focus
`.tsx, .jsx, *.css`	`frontend-specialist`	Component quality, a11y, performance
`.ts (server), .py`	`backend-specialist`	API design, security, error handling
`.test.`	`test-engineer`	Test quality, coverage gaps
`prisma/, migrations/`	`database-architect`	Schema quality, query performance
`Dockerfile, CI/*`	`devops-engineer`	Config quality, security
All files	`security-auditor`	Vulnerabilities, secrets, OWASP

Synthesize findings
- Combine all agent findings
- Prioritize by severity
- Provide actionable fixes

Output Format

## Code Review Report

### Scope
[Files reviewed, line count]

### Summary
| Severity | Count |
|----------|-------|
| Critical | X |
| Warning  | X |
| Info     | X |

### Findings

#### Critical
1. **[File:Line]** - [Issue description]
   - Why: [Explanation]
   - Fix: [Code suggestion]

#### Warnings
1. **[File:Line]** - [Issue description]
   - Fix: [Suggestion]

#### Suggestions
1. **[File:Line]** - [Improvement idea]

### Verdict
[APPROVE / REQUEST CHANGES / NEEDS DISCUSSION]

Read the full file on GitHub · 135 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 135 lines · 43 tokens per session scan A 5df2d4b03bec

Subscribe to this mod's changes

review is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 6mo ago), licensed MIT. It adds 43 tokens to every session and 838 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens

bilge-development-kit: Skill for Claude Code