code-quality-loop
Skill3 starsChanged 6 months agoApache-2.0View on GitHub
Iterative review-fix loop on the uncommitted change: with lifecycle on, reviews, fixes, simplifies and consolidates tests, as a paired-session review-only run (`run --review-only`). Use when the user wants the uncommitted change reviewed and fixed until clean ('clean up my changes', 'review and fix my diff', 'polish this before I commit', 'run code-quality-loop'). Not for a report-only or PR review (use review-pr), new work from a work item (use review-loop) or a pure file restructure (use reorganize).
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- guideSkill
- paired-sessionSkill
- review-loopSkill
- review-prSkill
- guideSkill
- paired-sessionSkill
- reorganizeSkill
- review-loopSkill
- review-prSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 47
If the paired-session skill reports stage A failure: <reason>, report code-quality-loop: paired-session entry refused (<reason>) and stop …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Code Quality Loop
Automated code review cycle: review -> fix -> re-review until clean. Focuses on code-level quality (correctness, style, error handling, tests). It runs as a paired-session review-only run (Step 0).
Step 0 — Entry: paired route (the legacy workflow was removed in v2.13.0)
Resolve entry in .review-loop/config.md (exact values legacy and paired-session): legacy is refused with
code-quality-loop: the legacy workflow was removed in v2.13.0; remove "entry: legacy" from .review-loop/config.md (paired-session is the only entry); an invalid value prints
code-quality-loop: entry "<v>" is not valid (paired-session is the only entry); using paired-session, a duplicate key or
an unreadable config prints code-quality-loop: entry could not be read (<reason>); using paired-session, and both
continue as absent. Then:
--legacyin$ARGUMENTS: refused withcode-quality-loop: the legacy workflow was removed in v2.13.0; run /review-loop:code-quality-loop without --legacy.- A host that is neither macOS (
uname -sisDarwin) nor native Windows (Git Bash:uname -sstarts withMINGW64_NT-orMSYS_NT-): refused withcode-quality-loop: paired-session needs macOS or native Windows; Linux (WSL included) and other hosts are not supported. - Otherwise the paired route. This skill owns the notice lines of steps 1 and 3: print each verbatim as visible reply text (not only in a tool call), as the first output after resolving
entryand before any other tool call or skill invocation, also on a headless run. The paired-session skill prints them only when they are missing.- Print
code-quality-loop: paired-session review-only run (entry set in .review-loop/config.md)when the key is set, orcode-quality-loop: paired-session review-only run (the default entry)when it is absent. - Map the arguments; a refused one stops here with its line, before any handoff:
[max-rounds]N: an integer of at least 2 becomes--max-exec-rounds N(round 1 reviews the existing change; blocking reviews at the cap end in a HOLD) and wins oversoft_limit_exec; absent, the paired-session skill's usual mapping applies (soft_limit_exec, else the coordinator default). Anything else is refused:code-quality-loop: max-rounds must be an integer of at least 2 on the paired route (round 1 reviews the existing change).--skip-reorganize: printcode-quality-loop: --skip-reorganize has no effect; the paired route never reorganizes.--reorganize: refused,code-quality-loop: reorganize is not part of the paired route; run /review-loop:reorganize <files> after the run.- Any other argument: refused,
code-quality-loop: unknown argument <arg>; usage: /review-loop:code-quality-loop [max-rounds]. auto_commit: falsein.review-loop/config.md: hand over--auto-commit false(absent ortrue: the review-only default, one local commit atacceptwith lifecycle on; off returns the uncommitted tree).judgment_modelorcheap_modelset in.review-loop/config.md: print, per key,code-quality-loop: <key> in .review-loop/config.md is not applied by paired-session; models come from the operator profile. (review_focus,review_styleandquality_focusare passed to the run by the paired-session skill.)
- Print
code-quality-loop: with lifecycle on, the paired route reviews, fixes, simplifies and consolidates tests. Acceptance normally makes one local commit (never a push;auto_commit: falsein .review-loop/config.md keeps it uncommitted). With lifecycle off, it stops after the gate; acceptance returns the uncommitted tree. It does not reorganize, run static-analysis artifacts, load a design document or sweep project docs. - Invoke the
paired-sessionskill with--code-quality-loopand the mapped--max-exec-rounds Nand--auto-commit false(if any), and end this skill. It follows the shared contract's Code-quality-loop entry: a review-only run on the uncommitted change with the quality writers on when lifecycle is on, ending at DONE (or HOLD);acceptwrites the delivery report. - If the paired-session skill reports
stage A failure: <reason>, reportcode-quality-loop: paired-session entry refused (<reason>)and stop (nothing falls back).
- Print
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.

