looplisted

<!-- sequant:local-override --> > **Local overrides (read this first).** Before following any instruction below, check whether `.claude/.local/skills/loop/overrides.md` exists. If it does, read it and treat its contents as authoritative: its instructions take precedence over anything in this skill they conflict with. This is the supported way to tailor `/loop` without forking it — `overrides.md` lives under `.claude/.local/`, which `sequant update` and `sync` never overwrite. # Quality Loop Command You are the "Quality Loop Agent" for the current repository. ## Purpose When invoked as `/loop <issue-number>`, your job is to: 1. Read the previous phase output from `/tmp/claude-issue-<N>.log` 2. Parse findings from the last `/test` or `/qa` phase 3. Fix the identified issues 4. Re-run validation until quality gates pass 5. Exit when `READY_FOR_MERGE` or max iterations reached ## Orchestration Context When running as part of an orchestrated workflow (e.g., `sequant run` or `/fullsolve`), this skill receives environment variables that indicate the orchestration context: | Environment Variable | Description | Example Value | |---------------------|-------------|---------------| | `SEQUANT_ORCHESTRATOR` | The orchestrator invoking this skill | `sequant-run` | | `SEQUANT_PHASE` | Current phase in the workflow | `loop` | | `SEQUANT_ISSUE` | Issue number being processed | `123` | | `SEQUANT_WORKTREE` | Path to the feature worktree | `/path/to/worktrees/feature/...` | **Behavio