refactor · diff

git:20260926.683e9ff to git:20260927.ec28a07

5 added, 6 removed. Audit A to A.

What this update changes in the checks

No check changed: every fixed check gives the same answer before and after this update.

A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.

---
name: refactor
- description: Re-check code just written or refactored against every applicable CLAUDE.md/AGENTS.md rule (user-level and project-level) before finishing. Use right after generating or modifying code; not for planning, reviewing someone else's existing code, or authoring policy.
+ description: Before finishing any file-changing task, delegate verification of all agent changes against user-level and project-level AGENTS.md and CLAUDE.md rules to an isolated subagent. Applies to every file type.
---
- - Before reporting a coding task done, re-read the current user-level and project-level CLAUDE.md/AGENTS.md files in full and check the code just written or changed against every rule verbatim — never rely on memory or a prior summary of those rules.
- - Fix any violation found in place; do not just note it or ask permission, unless fixing it would contradict the task's explicit scope or the user's explicit instruction.
- - If a rule conflicts with the task's explicit scope or an explicit user instruction, keep the task's instruction and report the conflict instead of silently breaking either one.
- - Limit the check to the lines added or changed for the current task; do not extend it to pre-existing unrelated code.
- - Skip this check when the task involved no code changes.
+ - Before reporting completion, start a read-only subagent named `verify` with a fresh context; do not inherit the conversation history. Give it the task objective, authorized scope, project root, applicable user-level instruction locations, and the exact current-task changes, including untracked and generated files. Identify pre-existing changes separately so they are not attributed to the task.
+ - Direct the subagent to read and follow [references/verify.md](references/verify.md). Keep that reference and full rule text out of the main context; receive only the compact verification result.
+ - Fix reported violations within the authorized scope, run required checks, and have the subagent re-check the resulting changes before reporting completion. Stop and report unresolved conflicts or fixes that require additional authorization; do not expand scope or silently waive rules.
+ - If subagents or fresh-context delegation are unavailable, report verification as incomplete. Do not fall back to reading all rules in the main context or claim compliance without verification.