No comments
Harness adaptation
Read the harness adaptation contract before delegating work, asking structured questions, selecting models, or locating harness state.
Spawn Comment Sicko. Act on accepted findings.
Authoring agents defend comments. Defer to Comment Sicko'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.
Steps
- Spawn a subagent to complete this task. Have it read
references/comment-sicko.md, then pass the scope. Do not restate its rules.
- 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 KILLs. Restore deletions only with exact exceptions and scoped proof. Before accepting thin IMPORTANT or do not remove kills or keeps, run ps-how or ps-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 ps-no-comments.
- 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
ps-architect once for the accepted set and surrounding code. Stop at the sketch. Architect shapes. Step 4 implements.
- 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 ps-principle-fix-root-causes and ps-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.
- 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.
- Report the deletion count, restored comments, reruns, architect sketch, fixes, encoding offers, encodings, unenforced constraints, and other open work.
1---2name: ps-no-comments3description: Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.4license: MIT. See LICENSE.txt5---67# No comments89## Harness adaptation1011Read [the harness adaptation contract](../ps-poteto-mode/references/harness-adaptation.md) before delegating work, asking structured questions, selecting models, or locating harness state.121314Spawn Comment Sicko. Act on accepted findings.1516Authoring agents defend comments. Defer to Comment Sicko's fresh perspective.1718## Scope1920Use the caller's files or diff. Otherwise use the current diff against the base branch, default `main`, including the working tree.2122## Steps23241. Spawn a subagent to complete this task. Have it read `references/comment-sicko.md`, then pass the scope. Do not restate its rules.252. 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 `ps-how` or `ps-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 `ps-no-comments`.263. 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 `ps-architect` once for the accepted set and surrounding code. Stop at the sketch. Architect shapes. Step 4 implements.274. 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 **ps-principle-fix-root-causes** and **ps-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.285. 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.296. Report the deletion count, restored comments, reruns, architect sketch, fixes, encoding offers, encodings, unenforced constraints, and other open work.
gannonh