Implement
sickn33/agentic-awesome-skills
Implement a piece of work based on a PRD or set of issues. An agent skill from sickn33/agentic-awesome-skills.
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE.
$ npx skills add sangrokjung/claude-forge --skill review-loop -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sangrokjung/claude-forge review-loop --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sangrokjung/claude-forge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/review-loop .claude/skills/review-loop && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "review-loop" agent skill from https://github.com/sangrokjung/claude-forge/tree/main/skills/review-loop into .claude/skills/review-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-loop", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sangrokjung/claude-forge/tree/main/skills/review-loopType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sangrokjung/claude-forge --skill review-loop -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sangrokjung/claude-forge review-loop --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sangrokjung/claude-forge.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/review-loop .agents/skills/review-loop && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "review-loop" agent skill from https://github.com/sangrokjung/claude-forge/tree/main/skills/review-loop into .agents/skills/review-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-loop", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sangrokjung/claude-forge --skill review-loop -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sangrokjung/claude-forge review-loop --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sangrokjung/claude-forge.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/review-loop .cursor/skills/review-loop && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "review-loop" agent skill from https://github.com/sangrokjung/claude-forge/tree/main/skills/review-loop into .cursor/skills/review-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-loop", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sangrokjung/claude-forge.git --path skills/review-loop--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sangrokjung/claude-forge --skill review-loop -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sangrokjung/claude-forge review-loop --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sangrokjung/claude-forge.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/review-loop .gemini/skills/review-loop && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "review-loop" agent skill from https://github.com/sangrokjung/claude-forge/tree/main/skills/review-loop into .gemini/skills/review-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-loop", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sangrokjung/claude-forge review-loopInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sangrokjung/claude-forge --skill review-loop -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sangrokjung/claude-forge.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/review-loop .github/skills/review-loop && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "review-loop" agent skill from https://github.com/sangrokjung/claude-forge/tree/main/skills/review-loop into .github/skills/review-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-loop", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sangrokjung/claude-forge --skill review-loop -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sangrokjung/claude-forge review-loop --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sangrokjung/claude-forge.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/review-loop .opencode/skills/review-loop && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "review-loop" agent skill from https://github.com/sangrokjung/claude-forge/tree/main/skills/review-loop into .opencode/skills/review-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-loop", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
review-loopRun the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE.
Review Loop is an agent skill from sangrokjung/claude-forge. Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified", "is this actually done", "maker checker", "second pair of eyes on this change". Not for prose, docs or typo edits.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/convergence-detection.md`).
The repository describes itself as: oh-my-zsh for Claude Code — 16 agents, 35 commands, 32 skills, 21 safety hooks in one install. v4.0 adds an adversarial review loop: a second agent that never sees the first… The licence is MIT.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 34d881d. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Review Loop loads about 1.5k tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 111 tokens; SKILL.md has 789 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from sangrokjung/claude-forge at commit 34d881d, republished under its MIT licence (© sangrokjung). 789 words, ~1,485 tokens.
.claude/skills/review-loop/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Nobody grades their own exam. The maker implements, a separate fresh checker tries to break the claim, and the two alternate until the checker approves the code as it stands right now.
Any change to behaviour: executable code, shell/Python/JS/TS/SQL, CI/CD, hooks, commands, agent and skill definitions, runtime prompts, and configuration that changes what the system does.
Exempt: prose documentation, marketing copy, typos, and formatting that cannot change behaviour. When a documentation-only change also touches something a runtime reads, it is behavioural. If you are unsure which side a change falls on, treat it as behavioural.
File count and diff size are not exemptions. A one-line change to an authorization check is behavioural; a 900-line documentation reflow is not.
| Risk | Lanes required |
|---|---|
| Ordinary behavioural change | 1 independent checker |
| Auth, authorization, payments, access-control rules, secrets, destructive data changes, irreversible deploys | 2 lanes, run by different checkers: correctness plus the risk-specific angle (runtime security, or rollback) |
maker implements → targeted test / real-surface QA → fresh checker
↑ │
└────────── REQUEST_CHANGES ← findings ──────────────┘
│
APPROVE on current code → doneThere are exactly three verdicts: APPROVE, REQUEST_CHANGES, UNVERIFIED.
If a checker modifies the source, it has joined the maker set and its verdict is void. A past maker can never be that change's checker.
Implement. Keep the change inside the scope you declared. Unrelated cleanup that arrives in the same diff will be reviewed as part of it.
Produce evidence before dispatch. Run the targeted tests and, when the change has a surface a person uses, exercise that surface the way they would. Record the exact commands and their exit status. Evidence from before your last edit is stale.
Dispatch a fresh checker. Use the Task/Agent tool to spawn adversarial-reviewer in its own
context, or a general-purpose agent given that agent's contract. Hand it:
git rev-parse HEAD).Do not hand it your conclusion. "I verified this works" is the claim under test, not context.
Read the verdict, not the tone. A checker that praises the change but lists a HIGH finding has returned REQUEST_CHANGES. A checker that died mid-run has returned UNVERIFIED, however encouraging its last message was.
Fix and re-dispatch. Every round gets a checker with a fresh context. Reusing the previous checker means asking someone to re-read their own conclusion.
Stop when a current APPROVE exists for the code as it stands, backed by evidence from that same revision.
When you come back for round N+1, say so plainly:
Both of the defects worked through in docs/VERIFICATION-LOOP.md were found this way: the first
review broke the guard, and the review of the fix broke the fix.
Three rounds on the same strategy is not a reason to stop, and it is not a reason to keep going
unchanged. Switch strategy: a different reproduction, a narrower test, a different checker or
runtime, or a re-plan of the approach. See references/convergence-detection.md.
Escalate to the human when the same finding comes back REQUEST_CHANGES twice in a row: two failed
attempts at one defect means the diagnosis is wrong, and a third attempt usually makes it worse.
Report the finding, both attempted fixes, and the reproduction. See rules/adversarial-review.md.
In every one of those cases the honest report is what is missing, not "done".
© sangrokjung, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in skills/review-loop of sangrokjung/claude-forge.
Open the folder on GitHubat commit 34d881d
Review Loop next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Review Loop this skillsangrokjung/claude-forge | 852 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Implementsickn33/agentic-awesome-skills | 47k | 5 repos | ~306 | Automated safety check: Pass | MIT | |
| Implementcodewhale-hq/Codewhale | 41k | — | ~190 | Automated safety check: Pass | MIT | |
| Incremental Implementationaddyosmani/agent-skills | 103k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Implementbestofjs/bestofjs | 3.1k | 18 repos | ~109 | Automated safety check: Pass | MIT | |
| ImplementAutomattic/simplenote-android | 1.9k | — | ~1.1k | Automated safety check: Pass | GPL-2.0 |
sickn33/agentic-awesome-skills
Implement a piece of work based on a PRD or set of issues. An agent skill from sickn33/agentic-awesome-skills.
codewhale-hq/Codewhale
Carry an authorized, defined request or approved plan through scoped edits and proportionate verification.
addyosmani/agent-skills
Delivers a change in thin vertical slices, each implemented, tested, verified and committed before the next, using vertical, contract-first or risk-first slicing.
bestofjs/bestofjs
Implement a piece of work based on a spec or set of tickets.
Automattic/simplenote-android
End-to-end implementation workflow: plan, implement, verify, commit, and open a draft PR.
ruvnet/ruflo
Run the SPARC Pseudocode and Architecture phases (2 and 3) — write algorithm pseudocode, design module boundaries and API contracts, then implement
sangrokjung/claude-forge
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack.
sangrokjung/claude-forge
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing.
sangrokjung/claude-forge
Analyze session work and automatically convert reusable patterns into Claude Code skills.
sangrokjung/claude-forge
A skill your agent uses when starting Claude Code projects, writing CLAUDE.md/spec.md, dispatching subagents, or requesting Agent Teams parallel development.
sangrokjung/claude-forge
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.
sangrokjung/claude-forge
Measure and shrink the always-loaded context of a Claude Code harness (CLAUDE.md + rules without paths frontmatter) back under budget — migrate narrative to reference files, convert rules to…
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Review Loop is an agent skill from sangrokjung/claude-forge. Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE.
Run `npx skills add sangrokjung/claude-forge --skill review-loop -a claude-code`. Or copy the skill folder (skills/review-loop in sangrokjung/claude-forge) into .claude/skills/review-loop in your project. Claude Code loads it when a task matches its description.
Run `npx skills add sangrokjung/claude-forge --skill review-loop -a codex`. Or copy the skill folder (skills/review-loop in sangrokjung/claude-forge) into .agents/skills/review-loop in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sangrokjung/claude-forge --skill review-loop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-loop, .gemini/skills/review-loop, .github/skills/review-loop and .opencode/skills/review-loop in your project.
Going by SKILL.md and its folder, Review Loop needs the command-line tools its instructions call (git).
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Review Loop is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 651 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Review Loop: Implement (sickn33/agentic-awesome-skills, 47k stars), Implement (codewhale-hq/Codewhale, 41k stars), Incremental Implementation (addyosmani/agent-skills, 103k stars) and Implement (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
sangrokjung (a GitHub user) maintains it in sangrokjung/claude-forge, which has 852 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on September 3, 2026.
Source: sangrokjung/claude-forge on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.