Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Review Apply

ASecurity

Batch-apply findings from the most recent --local review. One confirmation, one test run.

2 stars
0 votes
0 copies
0 views
Added 10/6/2026
ai-agentsbash

Security Analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned 10/6/2026

$npx -y skills add e128/dotnet-reference --skill review-apply --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Review Apply?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Review Apply
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/e128-review-apply/badge)](https://www.skillsdirectory.com/skills/e128-review-apply)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: review-apply
description: >
  Batch-apply findings from the most recent --local review. One confirmation, one test run.
when_to_use: "dispatched by review router"
argument-hint: "[--include-low]"
user-invocable: true
---

# Review: Apply Mode

Batch-apply findings from the most recent `--local` review. One confirmation, one test run.

## Phase 1: Load Findings

Load parsed findings from the latest `plans/review-*` dir (`tasks.md` preferred, `context.md` fallback), grouped by file with severity:
```bash
scripts/internal/review-findings.sh --json          # add --include-low to keep LOW findings
```
Each finding has `file`, `line`, `severity`, and `text`. LOW is skipped unless `--include-low`. If the script reports `"plan":null` → "No saved review found. Run `review --local` first."

Additionally skip: needs-verification, advisory-only, timed-out agents, known exceptions (see [references/known-exceptions.md](references/known-exceptions.md)).

## Phase 1.5: Edit Plan

Map each finding → exact file + line + planned edit. Group by file. If >10 files, warn "Large blast radius ({N} files)." Verify accuracy against current code (code may have changed since review).

## Phase 2: Triage

Display confirmation table. Auto-apply CRITICAL + HIGH + MEDIUM. Skip LOW unless `--include-low`.

## Phase 3: Batch Apply

Read all affected files first (parallel Reads), then apply all edits. Group findings by file, apply all in one Edit per file. Hold the test run until every fix is applied.

**Cascade stop rule:** If >5 test failures in files outside the edit plan, stop and report the cascade. Do not chase it.

**AskUserQuestion before:** public method/interface changes, >10 line deletions, test expectation changes.

## Phase 4: Verify

Spawn `build-validator` agent for changed files.

## Phase 4.5: Bounded Reflection Loop

Skip if Phase 4 passed cleanly and all fixes were mechanical. Cap N=2. Self-review → verify → cross-review per iteration.

## Phase 5: Report

```
Applied Findings
================
N findings applied across M files
Targeted tests: {N passed, M failed}
Files modified: ...
Not applied (manual review needed): ...
```

## Rules

- Read every file before editing. Re-read after format.
- One batch, one test run, run tests only after all fixes land.
- Skip LOW by default. Skip "needs verification" findings.
- Lode is out of scope: leave lode untouched by review findings.
- Tool-call budget: >100 calls → stop and report progress.

## References

- [references/known-exceptions.md](references/known-exceptions.md)

Attribution

e128e128
View sourceSee grades on GitHubMore from e128 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →