agentmods.dev

comprehensive-review

comprehensive-review is a skill for Claude Code from HirogaKatageri/hirokata. It costs 166 tokens per session (1,665 once invoked), scanned A, original, MIT.

A process for reviewing recent code changes across requirements, tests, edge cases, architecture, and security. Edge cases are unusual inputs or situations that can expose bugs.

In plain words
What is it for?
It is for checking whether changes are ready for a pull request or release, using requirements and the relevant code diff.
Why use it?
It brings several review perspectives together so gaps in implementation, robustness, design, or security are easier to spot before a pull request or deployment.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the guild plugin — 21 skills, 15 agents shipped together

not rated 5repo changed 8d ago A scan 166 tokens original MIT

Good fit It is for checking whether changes are ready for a pull request or release, using requirements and the relevant code diff.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hirogakatageri/hirokata/comprehensive-review
View source ↗ HirogaKatageri/hirokata
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 HirogaKatageri/hirokata --skill comprehensive-review
Clone the repo
git clone --depth 1 https://github.com/HirogaKatageri/hirokata

Made for: Claude Code.

Or install guild, the plugin that ships this one along with the rest of its 21 skills, 15 agents.

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.

agentmods badge for comprehensive-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/hirogakatageri/hirokata/comprehensive-review/github.svg)](https://agentmods.dev/skills/hirogakatageri/hirokata/comprehensive-review)
Your own site
<a href="https://agentmods.dev/skills/hirogakatageri/hirokata/comprehensive-review"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/comprehensive-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.

agentmods 80×15 button for comprehensive-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/hirogakatageri/hirokata/comprehensive-review"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/comprehensive-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 166 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,665 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00166 $0.01665
Opus 5 $0.00083 $0.00833
Sonnet 5 $0.00033 $0.00333
Haiku 4.5 $0.00017 $0.00167

Measured 8d ago against content hash 2aae5ba827fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

comprehensive-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 8d 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.

plugins/guild/skills/comprehensive-review/SKILL.md · 154 lines

How it starts

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

Comprehensive Review

Orchestrates five specialized review agents in parallel to provide a complete, multi-dimensional analysis of recent code changes:

  1. Requirements Compliance — Verifies all requirements are implemented
  2. Test Coverage — Ensures business logic is testable and tested
  3. Edge Case Handling — Identifies unhandled edge cases and boundary conditions
  4. Architectural Alignment — Checks compliance with clean architecture principles
  5. Security — Identifies vulnerabilities and risks (OWASP Top 10)

Review Workflow

Step 1: Identify Review Scope

  1. Find requirements documents — check the guild board first. If .guild/config.yaml exists, the board is a database, not a directory tree; read it with SQL (load guild:warehouse for the rules, notably that a body comes back byte-exact only when it is the one column you select):

    export PATH="$HOME/.turso:$PATH"
printf "SELECT id, status, title FROM requirement ORDER BY id;\n" | tursodb -q -m list .guild/guild.db
printf "SELECT body FROM requirement WHERE id = 'REQ-007';\n" | tursodb -q -m list .guild/guild.db
printf "SELECT body FROM plan WHERE requirement_id = 'REQ-007';\n" | tursodb -q -m list .guild/guild.db

    Keep -m list even for a single column: the default pretty mode draws a box and truncates long values with an ellipsis, which would silently hand you a clipped requirement to review against.

    Otherwise fall back to requirements/, docs/, planning/, or phase plan files. If none found, ask the user.

  2. Identify recent changes — use git log and git diff to understand scope

  3. Confirm scope — if unclear which requirements or commits to include, ask

Board-driven review of a guild requirement is normally handled by the check-in pipeline's reviewer gate; this skill is the read-only, on-demand surface for ad-hoc "am I ready?" checks.

Step 2: Launch All Five Agents in Parallel

Launch all agents in a single message using multiple Task tool calls. Include specific file paths and context in each prompt so agents don't waste time on discovery.

Read the full file on GitHub · 154 lines

Files

What ships with it

4 files 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.

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.

  1. 8d ago Changed · +13 lines 2aae5ba827fd
  2. 12d ago First seen · 141 lines · 166 tokens per session scan A c3caa85f0715

Subscribe to this mod's changes

comprehensive-review is a skill published in the GitHub repository HirogaKatageri/hirokata (5 stars, last pushed 3d ago), licensed MIT. It adds 166 tokens to every session and 1,665 once invoked, about $0.0008 per session on Opus 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.

Claude CodeCode reviewaiai-plugin
Related

Other skills, from other repositories

unslop-review

Rewrites code review comments so they read like a human teammate wrote them. Cuts corporate-AI throat-clearing ("I noticed...", "I was wondering if perhaps...", "It might be worth considering..."). Each comment is direct: location, the issue, a concrete fix. Use when user says "humanize review", "de-slop PR comment"…

MohamedAbdallah-14/unslop · 107 tokens

code-review

A code-review procedure that checks changed code by running available tests and type checks, then examining correctness, security, performance, style, and maintainability.

Today-Hbw/claude-code-dev-workflow · 22 tokens

autoreview

Pre-commit/ship code review: Codex default; optional Claude or Pi.

openclaw/clawhub · 20 tokens

omh-code-review

This is a Hermes-native code-review workflow skill.

rlaope/oh-my-hermes · 46 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

code-reviewer

Code review specialist focused on patterns, bugs, security, and performance.

RightNow-AI/openfang · 17 tokens