No comments

Delegate to a comment reviewer. Act on accepted findings.

Defer to the comment reviewer's fresh perspective.

Scope

Use the caller's files or diff. Otherwise use the current diff against the base branch, default main, including the working tree.

Compiler pragmas, preprocessor directives and tool-consumed annotations are not ordinary prose comments. Trace their owning compiler/tool contract. The reviewer flags any required changes for the coordinator; those changes belong in the scoped implementation/configuration work. Public API Haddock, including examples that specify the contract, qualifies for the existing public-contract exception.

Steps

1. Delegate to a comment reviewer using the complete reviewer instructions. Pass the scope. Follow the delegation instructions in AGENTS.md. Do not restate the reviewer rules.
2. Inspect its report and diff. Reject implementation-code edits, semantic-directive changes, scope escapes, exception-protected deletions, misstated MUST KILL reasons, and flags that treat kept intentional code as guilty. Reshape flags on our-code surprises stay actionable. Do not restore those comments. A keep survives only with scoped proof of an exception in the reviewer instructions; apply the full exception list. Audit missed scoped HLint and compiler-warning suppressions. Correctness or safety suppressions stay actionable MUST KILLs; handle semantic-directive changes through the scoped implementation steps, not comment-only deletion. Restore deletions only with exact exceptions and scoped proof. Before accepting thin IMPORTANT or do not remove kills or keeps, run /how or /why on their symbol. If a kill is ambiguous, do not restore. If a keep is refuted or still ambiguous, delete it. Revert and rerun one rejected report with the failure named. Reject a second, report it open, and fail /no-comments.
3. Fix trivial accepted flags directly by deleting a dead path, dropping a parameter, or using the real API. If any fix needs a shape, run /architect once for the accepted set and surrounding code. Stop at the sketch. Architect shapes. Step 4 implements.
4. Implement the smallest root-cause fix in scope. Remove every named workaround. If the root cause is out of scope, land the smallest in-scope fix and report the rest open. The principle-fix-root-causes and principle-redesign-from-first-principles skills guide intent only. Neither authorizes widening the fence nor fixing instances outside it. Never bolt on symptom guards.
5. Constraint comments say do not remove, do not change wording, or talk to X before changing. Leave comments that satisfy a proven exception in the reviewer instructions. Offer the cheapest in-scope type, runtime, test, or CI lint. Wait for interactive approval. Unattended and eval require caller pre-approval. If approved, encode then delete. Otherwise delete, report the constraint open, and sketch out-of-scope work.
6. Report the deletion count, restored comments, reruns, architect sketch, fixes, encoding offers, encodings, unenforced constraints, and other open work.