no-comments · diff

git:20260827.f7b391a to git:20260907.b1269d9

6 added, 13 removed. Audit A to A.

---

name: no-comments

- description: "Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints."

+ description: Review and simplify comments or suppressions within a requested code scope.

disable-model-invocation: true

---

# No comments

- Spawn Comment Sicko. Act on accepted findings.

- Authoring agents defend comments. Defer to Comment Sicko's fresh perspective.

+ Remove redundant narration, dead commented-out code, and stale explanations from the requested scope. Keep legal headers, public API contracts, and non-obvious reasons or constraints that code alone cannot explain.

- ## Scope

+ Use the supplied files or diff. Review nearby code before accepting a deletion. For uncertain comments, retain the information until evidence resolves it; uncertainty is not a reason to delete.

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

+ A `comment-sicko` read-only review can provide an independent pass when useful. The parent judges the findings and performs authorized edits. Do not launch **how**, **why**, or **architect** merely to adjudicate wording.

- ## Steps

+ Inspect suppressions against the compiler or lint rule they affect. Fix a real underlying issue when in scope; preserve necessary, justified suppressions. Do not remove a correctness constraint because its replacement needs separate authorization.

- 1. Spawn the `comment-sicko` agent. Pass the scope. Do not restate its rules.

- 2. Inspect its report and diff. Reject application-code edits, 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 proof it is about something we cannot change. Audit missed scoped lint and TypeScript suppressions. Correctness or safety suppressions stay actionable `MUST KILL`s. 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: fix real causes, redesign as if requirements always existed, never bolt on symptom guards. Neither authorizes widening the fence nor fixing instances outside it.

- 5. Constraint comments say `do not remove`, `do not change wording`, or `talk to X before changing`. Leave keeps about things we cannot change. 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.

+ Verify behavior when code changes. For comments alone, inspect the diff and run required formatting checks. Report material deletions, fixes, and unresolved concerns.