independent-review-loop
SolidIndependent review loop run before delivery in code work. An independent reviewer (Codex, or fresh Codex-style subagents) reads the whole PR against the approved outcome; the lead fixes in-scope functional findings and re-reviews until none remain. Its differentiator is independence and exhaustiveness — a reviewer that fails differently from the authors, run to clean — distinct from the recursive-refinement ladder. Invoked by the team lead from the unified pre-ship gate (code-mode and /swarm:refine) after the ship steps.
Install
Quality Score: 84/100
Skill Content
Details
- Author
- DheerG
- Repository
- DheerG/swarms
- Created
- 5 months ago
- Last Updated
- 1 months ago
- Language
- Shell
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
loop-review
Independently review one loop iteration's implementation diff against the product contract and report a verdict (APPROVE, REVISE with must-fix items, or — at the gate — ESCALATE to the human). Requirement-first — per-REQ satisfaction is judged before code quality; the gate renders a machine-parsed verdict per REQ. Runs read-only with fresh context; driven by loop.sh, not for ad-hoc use.
pr-review-loop
self-check before requesting independent review; never a merge verdict
review-loop
Multi-round adversarial code review loop — four specialized agents (correctness, adversarial, API design, test rigor) run in parallel against a PR, repeated until all four return `CLEAN — ship it` or a budgeted number of rounds (default 5) is exhausted — whichever comes first, with two ask-first soft stops in between (a NIT-only round; severity declining two rounds straight) so the loop pauses to check in on diminishing returns instead of always running to the cap. Use when the user wants a thorough review of a substantive PR — new interfaces, contract changes, load-bearing refactors — and has signalled they want both correctness AND polish. Heavy: up to 5 rounds × 4 agents = 20 sub-invocations, so not for tiny bug fixes, WIP sketches, or doc-only PRs. Invoke explicitly; do not auto-trigger from a generic "review this" request unless the user names the high-bar mandate.