[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75R69CM1SVD72YV99ABMFHA":3,"skill-same:01M75R69CM1SVD72YV99ABMFHA":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M75R69CM1SVD72YV99ABMFHA","thermo-nuclear-review",null,"Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch\u002FPR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.","TheDarkSkyXD\u002FSuperDevAgents","TheDarkSkyXD","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34119991?v=4","01M75491CAR2M915CJW2NKRTE7","01M75R09ATEWYMSRKW981X1EPY",1,"MIT","https:\u002F\u002Fgithub.com\u002FTheDarkSkyXD\u002FSuperDevAgents\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fthermo-nuclear-review\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: thermo-nuclear-review\ndescription: Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch\u002FPR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.\n---\n\n# Thermo Nuclear Review\n\nRead [the portable runtime contract](..\u002Fsuperdev-mode\u002Freferences\u002Fportable-runtime.md) before following this workflow.\n\nUse this skill for a comprehensive security and correctness audit of a checked-out branch.\n\n## Prompt\n\nYou are a security expert performing a comprehensive review of a checked out branch. Audit this branch and its changes extremely thoroughly for bugs, changes that break existing features\u002Ffunctionality, and security vulnerabilities. Be EXTREMELY thorough, rigorous, careful, ambitious, and attentive. NOTHING can slip through.\n\n# Scope\nONLY report issues related to code that is being ADDED or MODIFIED in this PR.\nFocus on changes in the diff.\nDO NOT report vulnerabilities in existing code that is not being changed.\n\n# Guidelines\n\n## Breaking Functionality Guidelines\nThis is a complex codebase, with many cross-package\u002Fmodule dependencies. Often simple code changes in one place have subtle interactions that break functionality elsewhere. You MUST be extremely thorough in tracing through possible side effects of the changes.\n\n## Breaking Devex Guidelines\nIt can be easy to break developers' ability to run \u002F build the code locally. You MUST catch changes that will impact users' developer experience. Some examples (not exhaustive):\n- Modifying how secrets are read \u002F where they are read from\n- Updating environment variable names \u002F adding environment variables\n- Remapping ports \u002F networking\n- Adding scripts that must be run for certain functionality to continue working. Broadly speaking these are changes that will modify the way developers currently run \u002F build the code. This does not include changes that introduce new alternative ways to run\u002Fbuild things. Adding dependencies with package managers does not count as a devex breaking change, unless it requires the user to do some very new thing that is not part of their normal development workflow, like manually installing software off of a website \u002F App Store.\n\n## Feature Leak Guidelines\nThe codebase might carefully gate features behind feature flags or internal-only checks. You MUST NOT allow any features that are meant to be behind a feature gate leak. These leaks are often subtle. Be VERY careful and thorough.\n\n## Intended Breakage Guidelines\nIf you identify a high risk finding, but the intent of the branch is to introduce that finding – e.g. break some functionality, remove a feature flag, remove a safeguard – AND the scope of the change is well constrained, you SHOULD NOT waste the author's time by reporting the issue to them. However, if you believe it is likely that they are not aware of the full implications of their change, or you are worried that they are under-weighting the negative impacts (extreme example: a developer pushes a PR titled \"Delete the database\"), or you are worried that the change is actually malicious, you should still report the finding.\n\n## Over-reporting Guidelines\nIf you report issues as High priority when they are not in fact high priority \u002F meaningful issues, devs will lose trust in you and stop listening to you over time.\nNEVER misreport the priority \u002F importance of issues. Be extremely thorough in tracing issues end-to-end to gain complete, and total confidence before reporting.\n\n# Final Response\nIF you have medium-to-high priority \u002F risk findings, and there is a PR for this branch, then check the PR\u002FMR discussion using gh\u002Fglab cli to see if there are comments from a review bot or others present.\nIf so, take their findings into account. If they found issues you missed, evaluate them to determine if they are valid and include them in your report. If they found some of the same issues you did, see if there is anything from their findings that are worth incorporating into your response.\nFlag issues found by a review bot or others in the PR\u002FMR discussion that you include in your report.\n\n\n# Critical Rules\n- NEVER present issues with unfinished research. E.g. Never say something like, \"The client has issue X, but if handled in the backend then this is ok.\" if you have access to the backend code and can check for yourself.\n- You MUST wait to check the PR\u002FMR discussion until AFTER you have performed your audit. This way you have fresh eyes while you review.\n- Be EXTREMELY thorough, rigorous, careful, ambitious, and attentive. NOTHING can slip through.\n","# Thermo Nuclear Review\n\nRead [the portable runtime contract](..\u002Fsuperdev-mode\u002Freferences\u002Fportable-runtime.md) before following this workflow.\n\nUse this skill for a comprehensive security and correctness audit of a checked-out branch.\n\n## Prompt\n\nYou are a security expert performing a comprehensive review of a checked out branch. Audit this branch and its changes extremely thoroughly for bugs, changes that break existing features\u002Ffunctionality, and security vulnerabilities. Be EXTREMELY thorough, rigorous, careful, ambitious, and attentive. NOTHING can slip through.\n\n# Scope\nONLY report issues related to code that is being ADDED or MODIFIED in this PR.\nFocus on changes in the diff.\nDO NOT report vulnerabilities in existing code that is not being changed.\n\n# Guidelines\n\n## Breaking Functionality Guidelines\nThis is a complex codebase, with many cross-package\u002Fmodule dependencies. Often simple code changes in one place have subtle interactions that break functionality elsewhere. You MUST be extremely thorough in tracing through possible side effects of the changes.\n\n## Breaking Devex Guidelines\nIt can be easy to break developers' ability to run \u002F build the code locally. You MUST catch changes that will impact users' developer experience. Some examples (not exhaustive):\n- Modifying how secrets are read \u002F where they are read from\n- Updating environment variable names \u002F adding environment variables\n- Remapping ports \u002F networking\n- Adding scripts that must be run for certain functionality to continue working. Broadly speaking these are changes that will modify the way developers currently run \u002F build the code. This does not include changes that introduce new alternative ways to run\u002Fbuild things. Adding dependencies with package managers does not count as a devex breaking change, unless it requires the user to do some very new thing that is not part of their normal development workflow, like manually installing software off of a website \u002F App Store.\n\n## Feature Leak Guidelines\nThe codebase might carefully gate features behind feature flags or internal-only checks. You MUST NOT allow any features that are meant to be behind a feature gate leak. These leaks are often subtle. Be VERY careful and thorough.\n\n## Intended Breakage Guidelines\nIf you identify a high risk finding, but the intent of the branch is to introduce that finding – e.g. break some functionality, remove a feature flag, remove a safeguard – AND the scope of the change is well constrained, you SHOULD NOT waste the author's time by reporting the issue to them. However, if you believe it is likely that they are not aware of the full implications of their change, or you are worried that they are under-weighting the negative impacts (extreme example: a developer pushes a PR titled \"Delete the database\"), or you are worried that the change is actually malicious, you should still report the finding.\n\n## Over-reporting Guidelines\nIf you report issues as High priority when they are not in fact high priority \u002F meaningful issues, devs will lose trust in you and stop listening to you over time.\nNEVER misreport the priority \u002F importance of issues. Be extremely thorough in tracing issues end-to-end to gain complete, and total confidence before reporting.\n\n# Final Response\nIF you have medium-to-high priority \u002F risk findings, and there is a PR for this branch, then check the PR\u002FMR discussion using gh\u002Fglab cli to see if there are comments from a review bot or others present.\nIf so, take their findings into account. If they found issues you missed, evaluate them to determine if they are valid and include them in your report. If they found some of the same issues you did, see if there is anything from their findings that are worth incorporating into your response.\nFlag issues found by a review bot or others in the PR\u002FMR discussion that you include in your report.\n\n\n# Critical Rules\n- NEVER present issues with unfinished research. E.g. Never say something like, \"The client has issue X, but if handled in the backend then this is ok.\" if you have access to the backend code and can check for yourself.\n- You MUST wait to check the PR\u002FMR discussion until AFTER you have performed your audit. This way you have fresh eyes while you review.\n- Be EXTREMELY thorough, rigorous, careful, ambitious, and attentive. NOTHING can slip through.\n",{"name":5,"description":7},"main","5440d26a8d527a55c691e544ae0e4e23e89e7157",".agents\u002Fskills\u002Fthermo-nuclear-review",0,"https:\u002F\u002Fgithub.com\u002FTheDarkSkyXD\u002FSuperDevAgents","https:\u002F\u002Fgithub.com\u002FTheDarkSkyXD","2026-11-12 09:54:48",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add TheDarkSkyXD\u002FSuperDevAgents --skill thermo-nuclear-review",{"tool":36,"command":37},"bunx","bunx skills add TheDarkSkyXD\u002FSuperDevAgents --skill thermo-nuclear-review",{"tool":39,"command":40},"pnpm","pnpm dlx skills add TheDarkSkyXD\u002FSuperDevAgents --skill thermo-nuclear-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTheDarkSkyXD\u002FSuperDevAgents\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fthermo-nuclear-review\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M75RDJ9BA2E6J9NNCB1N7K56","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\u002FTheDarkSkyXD\u002FSuperDevAgents\u002Fblob\u002Fmain\u002Fplugins\u002Fsuperdev\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M75RDFHCYADBVWTXG3AAZC09","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise update","https:\u002F\u002Fgithub.com\u002FTheDarkSkyXD\u002FSuperDevAgents\u002Fblob\u002Fmain\u002Fplugins\u002Fsuperdev\u002Fskills\u002Fwhat-did-i-get-done\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M75RDDK5WRB8PJ8PN7N6EWNZ","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002FTheDarkSkyXD\u002FSuperDevAgents\u002Fblob\u002Fmain\u002Fplugins\u002Fsuperdev\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M75RD9SZ9223AT30NA53XJ44","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002FTheDarkSkyXD\u002FSuperDevAgents\u002Fblob\u002Fmain\u002Fplugins\u002Fsuperdev\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75RD7H5QRBN7DDGHX76JE4J","universal-architecture","Apply responsibility-based architecture and enforce import boundaries. Use for code placement, architecture reviews, adapters, CLI entry points, platform sharing, and ESLint boundary rules.","https:\u002F\u002Fgithub.com\u002FTheDarkSkyXD\u002FSuperDevAgents\u002Fblob\u002Fmain\u002Fplugins\u002Fsuperdev\u002Fskills\u002Funiversal-architecture\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M75RD5G2WGMRJKS5F7R7EW6N","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002FTheDarkSkyXD\u002FSuperDevAgents\u002Fblob\u002Fmain\u002Fplugins\u002Fsuperdev\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[]]