How do I install the Review skill?

Run npx skillmds@latest add tomevault-io/review-7 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Review safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Review?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Review by tomevault-io — Agent Skill

Name: Review
Author: tomevault-io

File contents

Review (Audit & Refine)

Analyze code for correctness, safety, and efficiency. This skill supports two modes: Report (analysis only) and Refine (apply improvements).

Core Mandates

Evidence-First: Establish a baseline by running tests BEFORE the review.
Single-Pass: Evaluate all categories (Correctness, Complexity, Quality, Efficiency, Cleanliness) in one pass.
Standards: Strictly follow the Code Standards table in CLAUDE.md.
Mode Selection:
- Report: Output a categorized report (ERROR, WARN, NIT). End with Verdict: LGTM, LGTM with nits, or Needs work.
- Refine: Apply targeted, behavior-preserving changes to improve clarity and reduce technical debt.

Execution Workflow

Scope: Detect modified files, feature branch diffs, or staged changes.
Baseline: Run build and test to establish a "Green" starting state.
Analyze: Apply the Code Standards (referencing CLAUDE.md).
Action:
- Report Mode: Generate findings formatted as [SEVERITY] file:line - Issue -> Fix.
- Refine Mode: Edit files surgically. Use language-expert skills (rust-expert, etc.) for idiomatic patterns.
Verify: Run tests/linter after refinement to ensure behavior is unchanged.

Anti-Rationalization

Excuse	Reality
"Tests passed, so it's fine."	Reviews catch architectural flaws and security risks that tests miss.
"Refining might break it."	Small, behavior-preserving edits with Red-Green verification are safe and essential.
"Subagents are always better."	For small or local changes, the main agent is more efficient. Use subagents for context isolation.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: review-7description: Use when performing deep code analysis for correctness, safety, quality, or to simplify recently modified code. Trigger on feature completion, unpushed commits, or before merging significant changes.---# Review (Audit & Refine)Analyze code for correctness, safety, and efficiency. This skill supports two modes: **Report** (analysis only) and **Refine** (apply improvements).## Core Mandates- **Evidence-First:** Establish a baseline by running tests BEFORE the review.- **Single-Pass:** Evaluate all categories (Correctness, Complexity, Quality, Efficiency, Cleanliness) in one pass.- **Standards:** Strictly follow the `Code Standards` table in `CLAUDE.md`.- **Mode Selection:** - **Report:** Output a categorized report (`ERROR`, `WARN`, `NIT`). End with `Verdict: LGTM`, `LGTM with nits`, or `Needs work`. - **Refine:** Apply targeted, behavior-preserving changes to improve clarity and reduce technical debt.## Execution Workflow1. **Scope:** Detect modified files, feature branch diffs, or staged changes.2. **Baseline:** Run `build` and `test` to establish a "Green" starting state.3. **Analyze:** Apply the `Code Standards` (referencing `CLAUDE.md`).4. **Action:** - **Report Mode:** Generate findings formatted as `[SEVERITY] file:line - Issue -> Fix`. - **Refine Mode:** Edit files surgically. Use language-expert skills (`rust-expert`, etc.) for idiomatic patterns.5. **Verify:** Run tests/linter after refinement to ensure behavior is unchanged.## Anti-Rationalization| Excuse | Reality || :--- | :--- || "Tests passed, so it's fine." | Reviews catch architectural flaws and security risks that tests miss. || "Refining might break it." | Small, behavior-preserving edits with Red-Green verification are safe and essential. || "Subagents are always better." | For small or local changes, the main agent is more efficient. Use subagents for context isolation. |---> Converted and distributed by [TomeVault](https://tomevault.io/claim/nijaru) — claim your Tome and manage your conversions.

Frequently asked questions

Review