code-quality-loop

Code Quality Loop

Automated code review cycle: review -> fix -> re-review until clean. Focuses on code-level quality (correctness, style, error handling, tests).

Overview

Pre-loop:  language-specific agents -> fix (once per detected language)
Loop R1:   code-reviewer + silent-failure-hunter + comment-analyzer + type-design-analyzer -> triage -> fix
Loop R2+:  code-reviewer + silent-failure-hunter -> triage -> fix -> repeat
Finalize:  reorganize (if applicable) -> code-simplifier agent -> build -> test consolidation -> pr-test-analyzer

Arguments

$ARGUMENTS: Optional flags and max round count.

• Max rounds: /code-quality-loop 3 — limit to 3 rounds (default: 5)
• Skip reorganize: /code-quality-loop --skip-reorganize — skip the Reorganize step in Finalize
• Force reorganize: /code-quality-loop --reorganize — always run Reorganize regardless of change size
• Combined: /code-quality-loop 3 --skip-reorganize

If neither --skip-reorganize nor --reorganize is specified, the Orchestrator decides automatically based on change scope (see Finalize Step 1).

Initialization

1. Scope: Always reviews git diff (unstaged changes), consistent with all internal review tools. Run git diff --name-only --diff-filter=d to identify changed files. If no changes found, abort with message "No changes to review."

2. Language detection: Detect languages from changed files:

   { git diff --name-only --diff-filter=d HEAD; git ls-files --others --exclude-standard; } | grep '\.' | sed 's/.*\.\([^.]*\)$/\1/' | sort -u
   

   Map file extensions to language-specific agents:

   • .go -> go-reviewer
   • .rs -> rust-reviewer
   • .py -> python-reviewer
   • .ts, .tsx, .js, .jsx, .html, .vue, .svelte -> frontend-security-reviewer

   Record the set of applicable language agents as language_agents.

3. Load design context (optional): Look for a design document in the project (e.g., openspec/changes/*/design.md, docs/design.md, or similar). If multiple exist, use the most recently modified one. If found, read it. This is the fix boundary constraint -- applies to all fix actions throughout this command (loop fixes, simplify, etc.). Do not deviate from design intent unless a design-level defect is found (security vulnerability, race condition, obvious logic error). If no design document is found, skip this constraint -- all fixes are allowed.