yamadashy/skills · Archived

claude-review-loop

Iterative Claude review-and-fix loop

First seen Jul 7, 2026

Installation

$ npx skills add yamadashy/skills --skill claude-review-loop

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from yamadashy/skills · top by installs.

npx skills add yamadashy/skills

Browse all from yamadashy/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 7
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,311 B
  • docs SUMMARY.md 62 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Repeat the following cycle on the current branch's changes against main (max 3 iterations):

  1. Review — Spawn a read-only Claude Code reviewer sub-agent over the diff (see the claude-exec skill for flag details):

``bash claude -p --no-session-persistence --permission-mode default \ --disallowedTools Bash,Edit,Write \ -- "Review the current branch's diff against main (git diff main...HEAD). Report only real defects — bugs, security issues, broken logic, missing edge cases. For each finding give file:line, severity, and a one-line fix. Skip style nitpicks and scope creep." ``

  1. Triage — Review agent findings and keep only what you also deem noteworthy. Classify each as Fix (clear defects, must fix) or Skip (style, nitpicks, scope creep). Show a brief table before changing anything.
  2. Fix only the "Fix" items. Keep changes minimal.
  3. Verify with npm run lint and npm run test. Fix any regressions and repeat this step until all checks pass before continuing.
  4. Re-review only the newly changed lines. Do not re-raise skipped items.

Stop when no "Fix" items remain or 3 iterations are reached. Print a summary of what was fixed and what was skipped.