← fstackCONTENT HISTORY

Update to fstack

Snapshot Sep 30, 2026 · 23:16 UTC · version 1.1.2

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Spawn the comment-sicko subagent, fix accepted findings, and offer encodings for claimed constraints.",
  "included_files": [],
  "name": "no-comments",
  "skill_md_contents": "---\r\nname: no-comments\r\ndescription: \"Spawn the comment-sicko subagent, fix accepted findings, and offer encodings for claimed constraints.\"\r\nmenu-description: strip comments before review, fix the accepted findings, encode claimed constraints\r\n---\r\n\r\n# No comments\r\n\r\nSpawn comment-sicko. Act on accepted findings.\r\n\r\nAuthoring agents defend comments. Defer to comment-sicko's fresh perspective.\r\n\r\n**Platform note.** On Codex, the `comment-sicko` subagent and the Claude tool names below are Claude defaults. Resolve them via [`codex-tools.md`](../engineer-mode/references/codex-tools.md).\r\n\r\n## Scope\r\n\r\nUse the caller's files or diff. Otherwise use the current diff against the base branch, default `main`, including the working tree.\r\n\r\n## Steps\r\n\r\n1. Spawn an `Agent` with `subagent_type: \"comment-sicko\"`. Pass the scope. Do not restate its rules.\r\n2. 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`.\r\n3. 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.\r\n4. 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.\r\n5. 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.\r\n6. Report the deletion count, restored comments, reruns, architect sketch, fixes, encoding offers, encodings, unenforced constraints, and other open work.\r\n"
}

SHA-256 of public snapshot: b4bd8f75b4b21ce4e5fbbb71897f35d6e9dca5f57fcc1a69f51888b429b7b981