[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSYRBBMNS77XC4M13MSS5P":3,"skill-same:01M7CSYRBBMNS77XC4M13MSS5P":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7CSYRBBMNS77XC4M13MSS5P","no-comments",null,"Spawn the comment-sicko subagent, fix accepted findings, and offer encodings for claimed constraints.","cameronjlarsen\u002Fengineering-toolkit","cameronjlarsen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F44081018?v=4","01M7CSW9ZZAK2D9T98W54VH45D","Cameron Larsen","01M7CSWA0JXH6RTFHGH204RA7F",0,"MIT","https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\u002Fskills\u002Fno-comments\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: no-comments\ndescription: \"Spawn the comment-sicko subagent, fix accepted findings, and offer encodings for claimed constraints.\"\n---\n\n# No comments\n\nSpawn comment-sicko. Act on accepted findings.\n\nDefer to comment-sicko's fresh perspective.\n\n**Platform note.** On Codex or another non-Claude runtime, the `comment-sicko` subagent and the Claude tool names below are Claude defaults. Resolve them via [`codex-tools.md`](..\u002Fengineering-mode\u002Freferences\u002Fcodex-tools.md).\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 an `Agent` with `subagent_type: \"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. Neither authorizes widening the fence nor fixing instances outside it. Never bolt on symptom guards.\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\nDefer to comment-sicko's fresh perspective.\n\n**Platform note.** On Codex or another non-Claude runtime, the `comment-sicko` subagent and the Claude tool names below are Claude defaults. Resolve them via [`codex-tools.md`](..\u002Fengineering-mode\u002Freferences\u002Fcodex-tools.md).\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 an `Agent` with `subagent_type: \"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. Neither authorizes widening the fence nor fixing instances outside it. Never bolt on symptom guards.\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},"main","e14e605d32e02d75d3bef1e20c21ccaa8ac05310","plugins\u002Fengineering-toolkit\u002Fskills\u002Fno-comments","https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit","https:\u002F\u002Fgithub.com\u002Fcameronjlarsen","Software Engineer @TheMortgageOffice ","2026-11-04 08:21:41",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add cameronjlarsen\u002Fengineering-toolkit --skill no-comments",{"tool":37,"command":38},"bunx","bunx skills add cameronjlarsen\u002Fengineering-toolkit --skill no-comments",{"tool":40,"command":41},"pnpm","pnpm dlx skills add cameronjlarsen\u002Fengineering-toolkit --skill no-comments","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\u002Fskills\u002Fno-comments\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7CT26RDV1NYPCSKMF6J22D6","work-unit-commits","Plan commits as reviewable work units. Trigger: implementation, commit splitting, stacked PRs, or keeping tests and docs with code.","https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\u002Fskills\u002Fwork-unit-commits\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7CT229DK7GNGZAC9EK10HKQ","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\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7CT20NV7VM98JYJ8ZGPJRDS","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise update","https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\u002Fskills\u002Fwhat-did-i-get-done\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7CT1ZDKYE78ZM563M21Y5YW","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7CT1XX1VGTG1PA3P90ZRCDZ","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7CT1T7J6555NF1ZY5YCKX7W","thermo-nuclear-code-quality-review","Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.","https:\u002F\u002Fgithub.com\u002Fcameronjlarsen\u002Fengineering-toolkit\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering-toolkit\u002Fskills\u002Fthermo-nuclear-code-quality-review\u002FSKILL.md",[],[]]