A code-review guide for checking changed code against an organisation’s quality, security and coding standards.

It helps review pull requests, merge requests, files or modules, run automated checks, and perform focused security, quality or test reviews.

It gives reviews a consistent structure and helps catch correctness, security, testing and maintainability problems before code is merged.

code-review — Skill for Claude Code and Codex by bdiasti

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add bdiasti/maestro-bundle-cli --skill code-review

Clone the repo

git clone --depth 1 https://github.com/bdiasti/maestro-bundle-cli

Made for: Claude Code, Codex.

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/bdiasti/maestro-bundle-cli/code-review/github.svg)](https://agentmods.dev/skills/bdiasti/maestro-bundle-cli/code-review)

Your own site

<a href="https://agentmods.dev/skills/bdiasti/maestro-bundle-cli/code-review"><img src="https://agentmods.dev/badge/skills/bdiasti/maestro-bundle-cli/code-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/bdiasti/maestro-bundle-cli/code-review"><img src="https://agentmods.dev/badge/skills/bdiasti/maestro-bundle-cli/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 951 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.00035	$0.00951
Opus 5.5	$0.00014	$0.00380
Sonnet 5.5	$0.00007	$0.00190
Haiku 4.5	$0.00003	$0.00095

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

Security

Grade A, and why

code-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.

templates/bundle-base/skills/code-review/SKILL.md · 140 lines

How it starts

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

Code Review

Perform structured code reviews following the organization's quality, security, and pattern standards.

When to Use

When asked to review a pull request or merge request
When evaluating code quality of a file or module
When a developer asks for feedback on their code
Before approving a merge

Available Operations

Full PR review with categorized feedback
Focused review (security-only, quality-only, tests-only)
Quick review of a single file
Compliance check against organization patterns

Multi-Step Workflow

Step 1: Gather Context

Read the changed files and understand the purpose of the changes.

# If reviewing a PR/MR
git diff main...HEAD --stat
git diff main...HEAD
git log main...HEAD --oneline

# If reviewing specific files
git diff --cached

Step 2: Run Automated Checks

Execute linters, tests, and static analysis before manual review.

# Backend (Java/Spring)
./mvnw checkstyle:check
./mvnw test

# Frontend (Angular)
npm run lint
npm run test

Step 3: Apply Review Checklist

Correctness:

Does the code do what the task/spec requires?
Are edge cases covered?
Are exception flows handled?

Quality:

Files with more than 500 lines? Split them.
Functions with more than 20 lines? Extract.
Nested ifs (hadouken)? Use early return.
Descriptive names? (calculateComplianceScore > calc)
Duplicated code? Extract if repeated 3+ times.
Dead code? Remove it.

Security:

Inputs validated at boundaries?
Hardcoded secrets? REJECT.
SQL injection possible? Use parameterized queries.
Rate limiting present on APIs?

Tests:

Unit tests for business rules?
Descriptive test names?
Tests cover happy path AND alternative flows?

Patterns:

Commit follows Conventional Commits?
Branch follows naming convention?
Directory structure by domain?
Project ubiquitous language respected?

Step 4: Categorize and Deliver Feedback

Use these categories for each comment:

Read the full file on GitHub · 140 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

references/review-checklist.md 1.5 KB

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 · 140 lines · 35 tokens per session scan A a36a14194a5f

Subscribe to this mod's changes

code-review is a skill published in the GitHub repository bdiasti/maestro-bundle-cli (22 stars, last pushed 7mo ago), licensed MIT. It adds 35 tokens to every session and 951 once invoked, about $0.0001 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-30.

Code review

code-review next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
code-reviewbdiasti/maestro-bundle-cli	Skill	22	7mo ago	MIT	A	35	Claude Code, Codex
autoreviewopenclaw/clawhub	Skill	9.6k	today	MIT	A	17	Claude Code, Codex
omh-code-reviewrlaope/oh-my-hermes	Skill	5.6k	today	MIT	A	20	Claude Code
agent-teams-simplify-and-hardenLeoYeAI/openclaw-master-skills	Skill	2.2k	7d ago	MIT	A	115	Claude Code, Codex
revdiff-planumputun/revdiff	Skill	956	today	MIT	A	84	Claude Code
re0-mergeLilMGenius/paperthin	Skill	1.4k	2d ago	MIT	A	51	Claude Code, Codex
explore-unknownsdzhng/skills	Skill	1.5k	yesterday	MIT	A	162	Claude Code, Codex