[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78BD4WNK8Z8N7ECJGEN5FEV":3,"skill-same:01M78BD4WNK8Z8N7ECJGEN5FEV":44},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":43},"01M78BD4WNK8Z8N7ECJGEN5FEV","thermo-nuclear-code-quality-review",null,"Run an opt-in strict maintainability review for giant files, spaghetti growth, misplaced logic, weak boundaries, unnecessary abstractions, and missed structural simplifications. Use for a thermonuclear review, harsh code-quality audit, code-judo review, or a file approaching 1000 lines. Do not use as an automatic rewrite mandate or for cosmetic cleanup.","hermes-jarvis-bot\u002Fhermes-agent-config-kit","hermes-jarvis-bot","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F288284026?v=4","01M78AV3BBD4M67J3YWSQRKP1Q","01M78AV3C2SKH53E0PZMXAKTTS",1,"MIT","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fdevelopment\u002Fthermo-nuclear-code-quality-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: thermo-nuclear-code-quality-review\ndescription: Run an opt-in strict maintainability review for giant files, spaghetti growth, misplaced logic, weak boundaries, unnecessary abstractions, and missed structural simplifications. Use for a thermonuclear review, harsh code-quality audit, code-judo review, or a file approaching 1000 lines. Do not use as an automatic rewrite mandate or for cosmetic cleanup.\ndisable-model-invocation: true\n---\n\n# Strict Code Quality Review\n\nThis is an unusually demanding review mode, not an instruction to rewrite code\nby taste. Inspect the current diff and surrounding architecture, then report\nonly high-conviction findings grounded in a contract, reachable behavior, or a\nmaterial maintainability risk.\n\n## Review Bar\n\nAsk:\n\n- Can a simpler ownership boundary remove whole branches or concepts?\n- Did the diff add ad-hoc flags, special cases, or feature logic to a shared\n  path instead of using the canonical layer?\n- Did a cohesive module become more coupled or cross a meaningful shape limit?\n- Are wrappers, casts, optionality, and sequential orchestration earning their\n  complexity?\n- Does a proposed decomposition reduce what a reader must hold in mind, rather\n  than merely move the same complexity into more files?\n\nA file crossing roughly 1000 lines is a strong signal to inspect decomposition,\nnot an automatic failure. Apply the project's actual shape policy and explain\nwhy a split would improve ownership. Do not manufacture a rewrite when the\ncurrent structure is coherent and the change is small.\n\n## Output\n\nReport findings in this order:\n\n1. structural regressions;\n2. missing simplifications with a concrete alternative;\n3. spaghetti or branching growth;\n4. boundary and type-contract problems;\n5. file shape and decomposition;\n6. lower-severity readability issues.\n\nFor each finding include file\u002Fline, contract or evidence, user\u002Foperator impact,\nand a concrete remedy. Separate `BLOCKER`, `ADVISORY`, and `ACCEPTED` decisions.\nIf no finding survives reachability, materiality, and evidence screening, say so.\n\n## Independence and scope\n\nUse a fresh reviewer for non-trivial changes. This review does not replace\nfocused tests, security proof, or `proof-verify`; it evaluates maintainability\nand architecture. It must not silently edit production code or turn an\nadvisory concern into a rewrite.\n\n## Gotchas\n\n- Ambition without a contract becomes over-engineering. Keep the selection gate:\n  a sufficient implementation is a reason to stop expanding.\n- A line count is a probe, not a universal design law.\n- Moving code across files without reducing coupling is not a successful\n  decomposition.\n- Passing tests do not erase a material architecture regression, but a style\n  preference without impact is not a blocker.\n\n## Troubleshooting\n\n| Symptom | Likely cause | Action |\n|---|---|---|\n| Review proposes a rewrite for a tiny diff | Scope or trigger was too broad | Limit the review to changed behavior and material risks |\n| Many low-value nits | No severity\u002Fmateriality screen | Keep only findings with evidence and an actionable remedy |\n| File is large but coherent | Threshold treated as a verdict | Record `ACCEPTED` with rationale and keep the stable boundary |\n| Suggested split adds more indirection | Complexity moved, not removed | Reject it and compare the reader's concepts before\u002Fafter |\n\n## Source\n\nAdapted from Cursor Team Kit's MIT-licensed `thermo-nuclear-code-quality-review`:\nhttps:\u002F\u002Fgithub.com\u002Fcursor\u002Fplugins\u002Ftree\u002Fmain\u002Fcursor-team-kit\u002Fskills\u002Fthermo-nuclear-code-quality-review\n","# Strict Code Quality Review\n\nThis is an unusually demanding review mode, not an instruction to rewrite code\nby taste. Inspect the current diff and surrounding architecture, then report\nonly high-conviction findings grounded in a contract, reachable behavior, or a\nmaterial maintainability risk.\n\n## Review Bar\n\nAsk:\n\n- Can a simpler ownership boundary remove whole branches or concepts?\n- Did the diff add ad-hoc flags, special cases, or feature logic to a shared\n  path instead of using the canonical layer?\n- Did a cohesive module become more coupled or cross a meaningful shape limit?\n- Are wrappers, casts, optionality, and sequential orchestration earning their\n  complexity?\n- Does a proposed decomposition reduce what a reader must hold in mind, rather\n  than merely move the same complexity into more files?\n\nA file crossing roughly 1000 lines is a strong signal to inspect decomposition,\nnot an automatic failure. Apply the project's actual shape policy and explain\nwhy a split would improve ownership. Do not manufacture a rewrite when the\ncurrent structure is coherent and the change is small.\n\n## Output\n\nReport findings in this order:\n\n1. structural regressions;\n2. missing simplifications with a concrete alternative;\n3. spaghetti or branching growth;\n4. boundary and type-contract problems;\n5. file shape and decomposition;\n6. lower-severity readability issues.\n\nFor each finding include file\u002Fline, contract or evidence, user\u002Foperator impact,\nand a concrete remedy. Separate `BLOCKER`, `ADVISORY`, and `ACCEPTED` decisions.\nIf no finding survives reachability, materiality, and evidence screening, say so.\n\n## Independence and scope\n\nUse a fresh reviewer for non-trivial changes. This review does not replace\nfocused tests, security proof, or `proof-verify`; it evaluates maintainability\nand architecture. It must not silently edit production code or turn an\nadvisory concern into a rewrite.\n\n## Gotchas\n\n- Ambition without a contract becomes over-engineering. Keep the selection gate:\n  a sufficient implementation is a reason to stop expanding.\n- A line count is a probe, not a universal design law.\n- Moving code across files without reducing coupling is not a successful\n  decomposition.\n- Passing tests do not erase a material architecture regression, but a style\n  preference without impact is not a blocker.\n\n## Troubleshooting\n\n| Symptom | Likely cause | Action |\n|---|---|---|\n| Review proposes a rewrite for a tiny diff | Scope or trigger was too broad | Limit the review to changed behavior and material risks |\n| Many low-value nits | No severity\u002Fmateriality screen | Keep only findings with evidence and an actionable remedy |\n| File is large but coherent | Threshold treated as a verdict | Record `ACCEPTED` with rationale and keep the stable boundary |\n| Suggested split adds more indirection | Complexity moved, not removed | Reject it and compare the reader's concepts before\u002Fafter |\n\n## Source\n\nAdapted from Cursor Team Kit's MIT-licensed `thermo-nuclear-code-quality-review`:\nhttps:\u002F\u002Fgithub.com\u002Fcursor\u002Fplugins\u002Ftree\u002Fmain\u002Fcursor-team-kit\u002Fskills\u002Fthermo-nuclear-code-quality-review\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","07d02526f424fc814f8350d6b0b728e81576603d","upstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fdevelopment\u002Fthermo-nuclear-code-quality-review",0,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot","2026-11-14 18:25:27",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":23},[33,36,39],{"tool":34,"command":35},"npx","npx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill thermo-nuclear-code-quality-review",{"tool":37,"command":38},"bunx","bunx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill thermo-nuclear-code-quality-review",{"tool":40,"command":41},"pnpm","pnpm dlx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill thermo-nuclear-code-quality-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fdevelopment\u002Fthermo-nuclear-code-quality-review\u002FSKILL.md",[],[45,51,58,65,72,79],{"skillNo":46,"name":47,"nameZh":6,"description":6,"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},"01M78BHH6VNT0MKZXGMP2F50X1","owner-voice","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Fowner-voice\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},"01M78BHD34XJHAK6EMZ7J1M80X","humanize-russian","Редактировать русский текст для ясности и естественного звучания, сохраняя факты,\nтермины, источники и жанр. Использовать когда: убрать канцелярит, сделать текст\nживее, отредактировать русский черновик или статью перед публикацией.\nНе определяет авторство и не обещает обход детекторов. Для английского —\nhumanize-english; для структуры и доказательств — article-structure-review.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Fhumanize-russian\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},"01M78BH9D09HCA7ECZMPEEAE5Y","humanize-english","Edit English drafts for clear, natural language while preserving facts, uncertainty,\ntechnical meaning, citations and genre. Use when: humanize this text, remove AI-style\nfiller, improve English prose, or edit an English article before publication.\nNot an authorship detector or a promise to bypass one. For Russian use\nhumanize-russian; for thesis\u002Fevidence and structure use article-structure-review.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Fhumanize-english\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},"01M78BH44Q25YMA16MC6FKZ2WY","caveman","Ultra-compressed reply mode. Cuts output tokens ~65-75% by answering in terse \"caveman\" style while keeping full technical accuracy, and shapes what survives: action first, state restated every turn, concrete time estimates, visible wins. Intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says \"caveman\", \"talk like caveman\", \"use caveman\", \"less tokens\", \"be brief\", or Russian \"пещерный режим\", \"говори как пещерный\", \"кратко\", \"меньше токенов\", \"экономь токены\" — or invokes \u002Fcaveman. Preserves the user's language (Russian in → Russian caveman out). Off only: \"stop caveman\" \u002F \"normal mode\" \u002F \"обычный режим\". Do not use merely because a response should be concise, and do not use when the user requests normal prose, a polished document, or exact wording.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Fcaveman\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},"01M78BGY0JTMTW3J3YE5RQTHCK","article-structure-review","Проверить структуру технической статьи после черновика: задача читателя, жанр,\nопора значимых утверждений на доказательства и честные ограничения.\nUse after the first draft, before publication. Исправлять структуру, когда это\nвходит в запрос; не создавать обязательный конвейер из других навыков.\nДля локальной языковой редактуры — humanize-english или humanize-russian.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Farticle-structure-review\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},"01M78BGRJYZGK1TNTCHWGY32W3","video-post-production","Video post-production rules: audio mastering, color, captions, platform export. Use when: 'add music', 'add voiceover', 'export for tiktok', 'add captions', 'color grade', 'audio levels', 'master audio', 'export settings', 'platform requirements'. Covers FFmpeg patterns, audio chain, subtitle standards, and platform-specific export configs. Do NOT use to generate or animate the video frames\u002Fscenes in code (use remotion-production-guide), to write the script (use video-narrative-arc), or to evaluate script quality (use script-evaluator); this is the finishing stage applied to an already-rendered video.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fvideo-production\u002Fvideo-post-production\u002FSKILL.md",[],[]]