generic-code-review

A workflow for reviewing code changes by gathering the target, researching its context, checking risks, and reporting findings before the summary.

In plain words
What is it for?
Use it to inspect a pull request, branch changes, or selected files and produce a risk-focused review report.
Why use it?
It makes code reviews more systematic and helps surface problems before conclusions are written.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/modiqo/skillspec/code-review
Any agent
npx skills add modiqo/skillspec --skill code-review
Clone the repo
git clone --depth 1 https://github.com/modiqo/skillspec

Made for: Claude Code, Codex.

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 511 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00025 $0.00511
Opus 5 $0.00013 $0.00255
Sonnet 5 $0.00005 $0.00102
Haiku 4.5 $0.00003 $0.00051

Measured 3d ago against content hash 5f8179a92221, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

generic-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 3d 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/code-review/SKILL.md · 48 lines

How it starts

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

Code Review

Review code changes by collecting the review target, researching context, checking risks, and reporting findings before summary.

This skill is a thin loader for the colocated skill.spec.yml. The spec is the source of truth for routes, rules, dependencies, imports, resources, recipes, tests, and trace requirements.

Runtime Contract

  1. Load ./skill.spec.yml from this skill folder before taking task actions.

  2. When the skillspec CLI is available, run:

    skillspec decide ./skill.spec.yml --input='<user task>' --trace-dir "${PWD}/.skillspec/traces"
    
  3. Strip skill invocation prefixes such as /my-skill, $my-skill, or /rote-shell-spec before passing --input.

  4. Preserve the emitted trace run_dir.

  5. When the CLI is available after a trace exists, run skillspec trace align ./skill.spec.yml --decision-trace <run_dir> and report the alignment status with the trace path.

  6. Follow the selected route, matched rules, forbids, elicitations, dependencies, imports, recipes, and closures from skill.spec.yml.

  7. If the CLI is unavailable, read skill.spec.yml directly and apply its rules manually. Do not expand this loader into a second source of truth.

Quick Commands

skillspec validate ./skill.spec.yml
skillspec imports check ./skill.spec.yml
skillspec test ./skill.spec.yml
skillspec deps check ./skill.spec.yml
skillspec explain ./skill.spec.yml --input='<user task>' --trace-dir "${PWD}/.skillspec/traces"
skillspec trace align ./skill.spec.yml --decision-trace "${PWD}/.skillspec/traces/<run-id>"

Completion Report

When reporting completion, include the selected route, the SkillSpec trace run_dir, the skillspec trace align status (pass, fail, or unproven), key failed or unproven alignment checks, and the concrete execution evidence ids or files.

Route Hints

  • current_pr: Review current pull request
  • diff_to_main: Review diff to main
  • specific_paths: Review specific paths
  • second_opinion: Provide review synthesis from supplied evidence

Read the full file on GitHub · 48 lines

Files

What ships with it

2 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. 3d ago First seen · 48 lines · 25 tokens per session scan A 5f8179a92221

Subscribe to this mod's changes

generic-code-review is a skill published in the GitHub repository modiqo/skillspec (737 stars, last pushed 24d ago), licensed Apache-2.0. It adds 25 tokens to every session and 511 once invoked, about $0.0001 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-30.

Related

Other skills, from other repositories

writing-e2e-flows

Use when a feature or fix in future-agi needs an end-to-end Playwright flow under e2e/ — a new flow for user-visible behaviour, an update to a flow whose pinned endpoint, route, table or selector changed, or when a review flagged missing E2E coverage. Also use to check whether an existing flow already pins an…

future-agi/future-agi · 174 tokens

reviewing-prs

Use when asked to review a pull request, branch, or diff — before approving, as a self-review before opening a PR, to judge whether a PR is ready — 'is PR 123 mergeable?', 'anything blocking here?' — or to answer 'does this change need an E2E flow'. Applies the FutureAGI coding standards and, in repos with an e2e/…

future-agi/future-agi · 129 tokens

ashfox

Create, edit, review, animate, and export game-ready low-poly assets in the ashfox web workbench through an AI agent. Use for low-poly modeling, deterministic textures and UVs, rigs, idle or motion animation, GLB, Bedrock, or GeckoLib exports, and Blockbench-free asset production.

sigee-min/ashfox · 67 tokens

ui-2026-cinematic

Cinematic 3D / scroll-driven / motion design skill for landing pages in 2026. Use when building marketing pages, SaaS sites, or product showcases that need scroll storytelling, 3D elements, micro-interactions, kinetic typography, or glassmorphism. Encodes modern best practices from Figma, Anthropic, Apple, Vercel.…

selectess/fde-consultants-protocoles · 99 tokens

template-skill

A minimal template for creating a new FDE Consultant Skill (Apache-2.0). Use as starting point for any new skill.

selectess/fde-consultants-protocoles · 31 tokens

production-autopsy

Start here. Audits a deployed ML or LLM or agent system that scores well on evaluation but fails, regresses, or behaves unexpectedly in production. Runs a reproducible root-cause "autopsy": frames the eval-to-deployment gap, reproduces the production failure, quantifies it by slice, tests confidence calibration under…

ByteStack-Labs/claude-plugins · 258 tokens