code-quality-loop

code-quality-loop is a skill for Claude Code from NYTC69/review-loop. It costs 76 tokens per session (1,130 once invoked), scanned A, original, Apache-2.0.

An iterative code-review and fix process that repeats until the code is clean or no further progress is possible.

In plain words
What is it for?
Use it on uncommitted code changes to review correctness, style, error handling, comments, types, tests, and code structure.
Why use it?
It reduces the need to coordinate separate review and repair passes and checks whether fixes actually resolve the findings.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the review-loop plugin — 6 skills, 12 agents shipped together

Good fit Use it on uncommitted code changes to review correctness, style, error handling, comments, types, tests, and code structure.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nytc69/review-loop/code-quality-loop
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add NYTC69/review-loop --skill code-quality-loop
Clone the repo
git clone --depth 1 https://github.com/NYTC69/review-loop

Made for: Claude Code.

Or install review-loop, the plugin that ships this one along with the rest of its 6 skills, 12 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for code-quality-loop

README.md
[![agentmods](https://agentmods.dev/badge/skills/nytc69/review-loop/code-quality-loop/github.svg)](https://agentmods.dev/skills/nytc69/review-loop/code-quality-loop)
Your own site
<a href="https://agentmods.dev/skills/nytc69/review-loop/code-quality-loop"><img src="https://agentmods.dev/badge/skills/nytc69/review-loop/code-quality-loop/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for code-quality-loop

Your own site · 80×15
<a href="https://agentmods.dev/skills/nytc69/review-loop/code-quality-loop"><img src="https://agentmods.dev/badge/skills/nytc69/review-loop/code-quality-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,130 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00076 $0.01130
Opus 5.5 $0.00030 $0.00452
Sonnet 5.5 $0.00015 $0.00226
Haiku 4.5 $0.00008 $0.00113

Measured 7d ago against content hash ad3ecdaed705, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

code-quality-loop scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/code-quality-loop/SKILL.md · 48 lines

How it starts

The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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:

  • --legacy in $ARGUMENTS: refused with code-quality-loop: the legacy workflow was removed in v2.13.0; run /review-loop:code-quality-loop without --legacy.
  • A host that is not macOS (uname -s is not Darwin): refused with code-quality-loop: paired-session needs macOS; Linux 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 entry and before any other tool call or skill invocation, also on a headless run. The paired-session skill prints them only when they are missing.
    1. Print code-quality-loop: paired-session review-only run (entry set in .review-loop/config.md) when the key is set, or code-quality-loop: paired-session review-only run (the default entry) when it is absent.
    2. 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 over soft_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: print code-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: false in .review-loop/config.md: hand over --auto-commit false (absent or true: the review-only default, one local commit at accept with lifecycle on; off returns the uncommitted tree).
      • judgment_model or cheap_model set 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_style and quality_focus are passed to the run by the paired-session skill.)
    3. 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: false in .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.
    4. Invoke the paired-session skill with --code-quality-loop and the mapped --max-exec-rounds N and --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); accept writes the delivery report.
    5. If the paired-session skill reports stage A failure: <reason>, report code-quality-loop: paired-session entry refused (<reason>) and stop (nothing falls back).

Read the full file on GitHub · 48 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago Changed · +4 tokens per session ad3ecdaed705
  2. 15d ago Changed · -614 lines · -22 tokens per session 29e670392bb2
  3. 16d ago Changed · +43 lines · +54 tokens per session e13fe34e173e
  4. 17d ago Changed ddb509df731d
  5. 21d ago Changed 255068b31d8f
  6. 25d ago Changed · +66 lines 63aea7d732fb
  7. 28d ago Changed · +1 lines 34b4cbc192cc
  8. 1mo ago Changed d6fe9d31193b
  9. 1mo ago First seen · 552 lines · 40 tokens per session scan A 0e21cb370df7

Subscribe to this mod's changes

code-quality-loop is a skill published in the GitHub repository NYTC69/review-loop (3 stars, last pushed today), licensed Apache-2.0. It adds 76 tokens to every session and 1,130 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

concept-audit

A read-only audit skill for checking code against Daniel Jackson concept models, which describe independent parts of a system and how they work together.

ontology-of-everything/SemanticSkills · 41 tokens

vet

Thorough codebase investigation that finds and fixes real problems. Maps architecture, scans every layer (structural, correctness, security, reliability, performance, hygiene), prioritized report with evidence, fix plan, executes collaboratively. A senior engineer doing a full review with authority to fix. Use when…

catcatcatstudio/cat-skills · 121 tokens

unused-code-audit

A code-audit skill for proving whether files, exports, functions, components, types, or helpers have real users before removal.

danhuaxiansheng/claude-code-cleanup-skills · 93 tokens

omc-review

Evaluate finished work for defects, risk, and simplification before it ships.

Yeachan-Heo/oh-my-claudecode · 18 tokens

audit

Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.

oliver-kriska/claude-elixir-phoenix · 35 tokens

code-review-web

Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug…

rampstackco/claude-skills · 121 tokens