[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CVPAD7FKDFE8RE2JAM3TQ6":3,"skill-same:01M7CVPAD7FKDFE8RE2JAM3TQ6":47},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7CVPAD7FKDFE8RE2JAM3TQ6","no-comments",null,"Spawn the comment-sicko subagent, fix accepted findings, and offer encodings for claimed constraints.","arjitj2\u002Fopen-pstack","arjitj2","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F15092149?v=4","01M7CVKN74D16AA1B4Y0CP3JKA","Arjit Jaiswal","01M7CVKN7SCSQVHE6GTQZC7XN6",16,"MIT","https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\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`](..\u002Fpoteto-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`](..\u002Fpoteto-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","264230bc14d9055d1333804799e7187e8e6e135c","plugins\u002Fpstack\u002Fskills\u002Fno-comments",2,"https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack","https:\u002F\u002Fgithub.com\u002Farjitj2","https:\u002F\u002Farjit.me\u002F","I want to work with great people to build great things that change the world.","2026-11-04 11:44:10",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add arjitj2\u002Fopen-pstack --skill no-comments",{"tool":39,"command":40},"bunx","bunx skills add arjitj2\u002Fopen-pstack --skill no-comments",{"tool":42,"command":43},"pnpm","pnpm dlx skills add arjitj2\u002Fopen-pstack --skill no-comments","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fno-comments\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7CVW5H20VXPF7Z01VXY20G2","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\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7CVW3937916EAX061GZTS4A","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise update","https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fwhat-did-i-get-done\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CVW0Z4XXRTZ4GGCW4CT95B","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CVVXMMWBB13598A412BXPR","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CVVSD76JCSPTD6P55K24B0","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\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fthermo-nuclear-code-quality-review\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CVVN2PRJKWMSXTH2G6SBWY","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\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[]]