[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DCP0SB0BH1E5P2E6QFFKB1":3,"skill-same:01M7DCP0SB0BH1E5P2E6QFFKB1":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":42},"01M7DCP0SB0BH1E5P2E6QFFKB1","no-comments",null,"Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.","harryhecanada\u002Fagent-skills","harryhecanada","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11355235?v=4","01M7DCMFGH1G7M5Z8PZ1DEZES4","01M7DCMFH4YERG90TH5YXC8MPQ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fharryhecanada\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fframeworks\u002Fengineering-rigor\u002Fskills\u002Fno-comments\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: no-comments\ndescription: \"Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.\"\ndisable-model-invocation: true\n---\n\n# No comments\n\nSpawn Comment Sicko. Act on accepted findings.\n\nAuthoring agents defend comments. Defer to Comment Sicko's fresh perspective.\n\n## Scope\n\nUse the caller's files or diff. Otherwise use the current diff against the base branch, default `main`, including the working tree.\n\n## Steps\n\n1. Spawn `delegate` with custom agent `comment-sicko`. Pass the scope. Do not restate its rules.\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 `\u002Fhow` or `\u002Fwhy` 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 `\u002Fno-comments`.\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 `\u002Farchitect` once for the accepted set and surrounding code. Stop at the sketch. Architect shapes. Step 4 implements.\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.\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.\n6. Report the deletion count, restored comments, reruns, architect sketch, fixes, encoding offers, encodings, unenforced constraints, and other open work.\n","# No comments\n\nSpawn Comment Sicko. Act on accepted findings.\n\nAuthoring agents defend comments. Defer to Comment Sicko's fresh perspective.\n\n## Scope\n\nUse the caller's files or diff. Otherwise use the current diff against the base branch, default `main`, including the working tree.\n\n## Steps\n\n1. Spawn `delegate` with custom agent `comment-sicko`. Pass the scope. Do not restate its rules.\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 `\u002Fhow` or `\u002Fwhy` 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 `\u002Fno-comments`.\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 `\u002Farchitect` once for the accepted set and surrounding code. Stop at the sketch. Architect shapes. Step 4 implements.\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.\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.\n6. Report the deletion count, restored comments, reruns, architect sketch, fixes, encoding offers, encodings, unenforced constraints, and other open work.\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","4a92ff09648713a9ba46b64f76094b89ee233308","skills\u002Fframeworks\u002Fengineering-rigor\u002Fskills\u002Fno-comments","https:\u002F\u002Fgithub.com\u002Fharryhecanada\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fharryhecanada","2026-10-09 23:00:59",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":23},[32,35,38],{"tool":33,"command":34},"npx","npx skills add harryhecanada\u002Fagent-skills --skill no-comments",{"tool":36,"command":37},"bunx","bunx skills add harryhecanada\u002Fagent-skills --skill no-comments",{"tool":39,"command":40},"pnpm","pnpm dlx skills add harryhecanada\u002Fagent-skills --skill no-comments","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fharryhecanada\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fframeworks\u002Fengineering-rigor\u002Fskills\u002Fno-comments\u002FSKILL.md",[],[44,51,58,65,72,79],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M7DCS5AAK976JJ881X7N3BN5","agent-roster","Use when delegating to a named subagent role (plan, logic, build, surgical, design, scribe, tester, advisor, hunter, sentinel, ship). Loads the role's brief, the dispatch shape, and its output schema.","https:\u002F\u002Fgithub.com\u002Fharryhecanada\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsubagents\u002Fagent-roster\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M7DCS0GF2V39E9T96TP4KBQF","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fharryhecanada\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fframeworks\u002Fengineering-rigor\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M7DCRXD5ABWB3ZYY1TX5T3JQ","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002Fharryhecanada\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fframeworks\u002Fengineering-rigor\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7DCRVP2KH8E037TX0EFC7KA","typescript-best-practices","TypeScript best practices. Use when reading or editing any.ts or.tsx file.","https:\u002F\u002Fgithub.com\u002Fharryhecanada\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fframeworks\u002Fengineering-rigor\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M7DCRR8E5M4NPBJ9T4P07PYN","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Ftechnical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002Fharryhecanada\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fframeworks\u002Fengineering-rigor\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7DCRMDT5EX1DGGDARATW6NC","teach","Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.","https:\u002F\u002Fgithub.com\u002Fharryhecanada\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fframeworks\u002Fengineering-rigor\u002Fskills\u002Fteach\u002FSKILL.md",[],[]]