review-loop
Skill1 starsChanged 4 months agoMITView on GitHub
Deep, iterative, evidence-based review of existing repository artifacts such as code, architecture, plans, specifications, prompts, skills, rules, configuration, documentation, tests, and release output. Use when asked to review, audit, harden, verify, or refine completed work; after productive changes covered by .claude/rules/loop-policy.md; or when reviewing the current session delta, an explicit target, or all session work. Produces an authority-aware local disposition for every real finding: persist it only when repository writes are authorized, otherwise name its exact proposed SSOT or task target as PENDING-AUTH.
59 other projects use a version of this.
Adopted by
Most recently taken up by
- DaraBoth/skilljmskilltheir own version, first seen Nov 15, 2026
- agentcrew-academy/harness-starter-kittheir own version, first seen Nov 15, 2026
- sp-hk2ldn/SKILLStheir own version, first seen Nov 15, 2026
- HerbertGao/herbertgao-skillstheir own version, first seen Nov 15, 2026
- fullstackhouse/skillstheir own version, first seen Nov 15, 2026
- revisit-studies/studytheir own version, first seen Nov 9, 2026
Used with
Projects with it also use motion-design, polish and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
soilmassSkillmotion-design
Create animations and motion graphics using industry standards. Use when asked to animate UI elements, create video content, implement transitions, or build motion systems. Implements W3C Design Tokens, Material Design 3 baseline, and Lottie specification compliance.
Also in 5 projects that use this
HK-hubSkillpolish
Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.
Also in 3 projects that use this
GoogleSkillto-spec
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Also in 4 projects that use this
GoogleSkillimprove-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Also in 5 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 4 projects that use this
MicrosoftSkillcouncil
Convene the persona panel — six orthogonal review lenses — on a target. Cold independent fan-out, debate-to-consensus, synthesized verdict with recorded dissent and a roster manifest.
Also in 3 projects that use this
- +4 more from google
Other versions59 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 59
- didi/mpx★ 4ksame name
- blockscout/frontend★ 310same name
- microsoft/bocpy★ 184same name
- 9thLevelSoftware/legion★ 76same name
- microsoft/Trieste★ 53same name
- revisit-studies/study★ 46same name
- timharris707/skills★ 44same name
- agentcrew-academy/harness-starter-kit★ 42same name
- spxrogers/agentsync★ 41same name
- Latand/delegatus★ 39same name
49 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- 1-csk-initSkill
- 2-csk-write-specSkill
- 3-csk-architectureSkill
- 4-csk-frontendSkill
- 5-csk-backendSkill
- 6-csk-qaSkill
- 7-csk-deploySkill
- audit-plan-loopSkill
- claude-skill-proxy-syncSkill
- create-worker-worktreeSkill
- csk-adopt-plan-scaffoldSkill
- csk-helpSkill
- csk-refineSkill
- csk-startSkill
- finish-branchSkill
- pull-main-ffSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. 0 are common, 16 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 52 edited versions we read keep these.
16
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Audit-only: default when the user asks to review, diagnose, inspect, or report.
- Very specific: line 18
Review + fix: use when the user explicitly requests fixes, uses --fix, or the review is a verification phase inside an already-authorized …
- Distinctive: line 21
Non-mutable target: always audit-only.
- Distinctive: line 23
Never commit, publish, deploy, contact another repository, or broaden scope unless the current request separately authorizes it.
- Distinctive: line 48
Always check these core dimensions:
- Distinctive: line 59
Add the applicable type lens:
- Distinctive: line 78
Read repository instructions and architecture before selecting commands.
- Distinctive: line 79
Use deterministic checks for mechanical facts and LLM judgment for semantic intent, coherence, omissions, and trade-offs.
- Distinctive: line 88
Never expose secrets, credentials, private data, or raw sensitive output.
- Distinctive: line 105
Do not silently filter uncertain high-impact suspicions.
- Very specific: line 113
Read AGENTS.md, CLAUDE.md, applicable skills/rules, and tasks/INDEX.md.
- Distinctive: line 125
REFINE: only in authorized Review + fix mode.
- Distinctive: line 128
CONVERGENCE: stop when no critical/high finding remains and another pass finds no substantial new issue.
- Distinctive: line 139
Check the in-scope set for contradictions, missing connections, ripple effects, interface drift, duplicated SSOT state, and whether the …
- Distinctive: line 146
Before fixing a critical/high finding below 90 confidence, ask an independent agent to try to disprove it when one is available.
- Very specific: line 152
Use --panel by assigning distinct dimensions to independent agents, then deduplicate their evidence.
- Distinctive: line 177
Use the narrowest existing SSOT.
- Distinctive: line 192
If the invariant does not balance, the review is not complete.
- Distinctive: line 202
every local disposition and the balanced completion invariant.
“Common” is measured: kept by at least 6 in 10 of the 52 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review Loop
Review existing work adversarially until coverage and evidence converge. The goal is to find real weaknesses, not to generate a long list or defend earlier work.
Determine Authority And Mode
Respect the authority of the current user request:
- Audit-only: default when the user asks to review, diagnose, inspect, or report. Read and verify, but do not mutate the reviewed artifacts.
- Review + fix: use when the user explicitly requests fixes, uses
--fix, or the review is a verification phase inside an already-authorized build/change task. Keep fixes inside that authorized scope. - Non-mutable target: always audit-only.
Never commit, publish, deploy, contact another repository, or broaden scope unless the current request separately authorizes it.
Resolve Scope
Choose one scope before reviewing:
- An explicit path, module, diff, PR, or named artifact overrides all defaults.
- With no target, review the current session delta: every artifact created or changed since the last completed review-loop pass. Include staged, unstaged, untracked, and committed session work plus non-code artifacts.
--allreviews all work produced in the session, even if reviewed earlier.--deepincreases depth, not scope.--panelrequests independent reviewers for distinct dimensions.
List the concrete inventory before classification. Do not sample silently. If earlier review coverage cannot be reconstructed after context compaction, state the uncertainty and use an explicit target or conservative full coverage.
For more than roughly eight materially different artifacts, present a compact coverage proposal and ask only if choosing full review versus risk-focused triage would materially change time or outcome.
Classify The Artifacts
Always check these core dimensions:
- correctness and consistency with requirements and SSOTs;
- completeness and missing paths;
- robustness, edge cases, and failure recovery;
- security, privacy, abuse, secrets, and data locality;
- performance, scalability, and resource use where relevant;
- interface, schema, and compatibility risk;
- maintainability, drift, and regression risk;
- evidence quality.
Add the applicable type lens:
| Type | Additional focus | Preferred evidence |
| Code/architecture | boundaries, concurrency, complexity, error handling, tests | project-native test/lint/typecheck/build/diff |
| Gate/guard | fail-closed behavior, bypasses, false positives/negatives | positive and negative trigger cases |
| Plan/spec/design | goals, acceptance criteria, assumptions, feasibility, alternatives | requirements and SSOT comparison |
| Config/infra/schema | safe defaults, validation, idempotence, migration/rollback, secrets | parser, validator, lint, dry run |
| Prompt/skill/rule | trigger precision, ambiguity, precedence, scope, counterexamples | validator plus realistic trigger/non-trigger cases |
| Documentation | accuracy against repository reality, paths, commands, links | path/link/command checks |
| Data/content | provenance, semantic consistency, completeness, sensitive data | source comparison plus LLM semantic review |
| Process/workflow | happy path, failures, ownership, restartability, lost-task risk | walkthrough and failure simulation |
Apply multiple lenses when an artifact has multiple roles. For an unknown type, derive and state the most relevant quality and failure dimensions from first principles.
Use Evidence Safely
- Read repository instructions and architecture before selecting commands.
- Use deterministic checks for mechanical facts and LLM judgment for semantic intent, coherence, omissions, and trade-offs.
- Show actual sanitized evidence: exit code, test result, diff, path/line, or fact checked against its source.
- Label anything that cannot be verified as
unverified; never report false green. - Inspect unfamiliar scripts and dependency hooks before executing them.
- Reuse existing processes where possible. Stop any temporary server, watcher, or process started solely for verification.
- Never expose secrets, credentials, private data, or raw sensitive output.
For code, explicitly consider injection, authorization, input validation, output encoding, path traversal, unsafe subprocesses, secrets, cryptography, deserialization, uploads, SSRF, concurrency, dependency risk, insecure defaults, and fail-open error handling when applicable.
Finding Model
Every finding records:
ID | artifact/location | dimension | severity | confidence | problem | evidence | recommendation | statusSeverity is critical, high, medium, or low. Confidence is 0–100 and
measures whether the diagnosis is correct, not its impact. Prioritize by both.
Do not silently filter uncertain high-impact suspicions; verify them before a
fix. Do not inflate style preferences or pre-existing unrelated issues into
findings.
Run The Review
Phase A: Scope And Baseline
- Read
AGENTS.md,CLAUDE.md, applicable skills/rules, andtasks/INDEX.md. - Inventory and classify every artifact in scope.
- Record Git/status baseline without modifying or hiding user changes.
- Select the project-native evidence for each artifact.
Phase B: Review Each Artifact
For each artifact, up to 12 iterations but stopping early on convergence:
- STAND: identify artifact, type, and intended contract.
- CRITIQUE: apply core dimensions, type lenses, edge cases, and evidence.
- DECIDE: select verified findings in severity/confidence order.
- REFINE: only in authorized Review + fix mode; use the smallest coherent change and preserve unrelated work.
- VERIFY: rerun the relevant checks and inspect the actual diff.
- CONVERGENCE: stop when no critical/high finding remains and another pass finds no substantial new issue.
Log compactly:
Artifact <path>, iteration N — findings: C/H/M/L | fixed: <IDs> | open: <IDs> | evidence: <result>Phase C: Cross-Artifact Pass
Check the in-scope set for contradictions, missing connections, ripple effects, interface drift, duplicated SSOT state, and whether the combined result solves the stated problem. This pass remains limited to artifacts and state inside the current repository.
Independent Verification
Before fixing a critical/high finding below 90 confidence, ask an independent agent to try to disprove it when one is available. Give it the artifact, claimed defect, applicable contract, and verification tooling, but not the desired conclusion. If no agent is available, perform and log a contrary refutation pass in the current context.
Use --panel by assigning distinct dimensions to independent agents, then
deduplicate their evidence. For a reproducible finding at confidence 90 or
above, a logged cause/fix confirmation may replace fan-out.
Phase D: Local Finding Disposition
Give every real finding exactly one terminal disposition. Persist findings only
when the current request already authorizes repository writes. In audit-only
mode without that authority, do not mutate a source of truth merely to satisfy
this phase; prepare the exact proposed target and use PENDING-AUTH.
FIX-DONE: fixed in authorized scope and verified.OWNER-SSOT: recorded in the relevant feature spec, master feature, architecture record, QA evidence, or release record.TASK-INDEX: continuation recorded once intasks/INDEX.mdthrough/csk-start, linked to its owner, only when it remains open/blocked, will span the current session, is explicitly deferred, or is a verified interruption point. Do not create and close a row for same-turn review/fix work.ASK: a material user decision is still required; persist a blocked task only when that decision must survive beyond the current session and repository writes are authorized.PENDING-AUTH: audit-only finding with an exact proposed local SSOT/task target, awaiting permission to persist it.DROP: false positive, accepted risk, or explicitly rejected item with reason.
Use the narrowest existing SSOT. Do not duplicate feature status in the task index. With write authority, keep the complete review record and every continuation inside the current repository. Without it, name that exact local target without writing.
The completion invariant is:
all findings == FIX-DONE + OWNER-SSOT + TASK-INDEX + ASK + PENDING-AUTH + DROP
undisposed findings == 0An ASK is durably complete only after its blocked continuation is stored
locally. PENDING-AUTH makes the read-only report complete but not durably
conserved; state that limitation and request one consolidated authorization.
If the invariant does not balance, the review is not complete.
Final Handoff
Report:
- scope and coverage;
- findings ordered by severity and confidence;
- fixes and actual verification evidence, if authorized;
- cross-artifact risks;
- every local disposition and the balanced completion invariant;
- anything unverified or deliberately not reviewed.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

