[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DQDNHVMPBZEME1MQHVM4AF":3,"skill-same:01M6DQDNHVMPBZEME1MQHVM4AF":62},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M6DQDNHVMPBZEME1MQHVM4AF","git:analyze-issue",null,"Analyze a GitHub issue and create a detailed technical specification","AntifragileTech\u002Fantifragile-claude-code","AntifragileTech","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F174357194?v=4","01M6DQCYMK4CDSQQAN0ZC72NTV","01M6DQCYS9YPW1WKMQ5TJMPQ43",9,"MIT","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fdev\u002Fanalyze-issue\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"git","analyze issue","analyze","issue","git:analyze issue","github","create","gh issue","Bash","gh","grep","technical","read","write","github issue","specification","2026-11-10 10:12:30",false,"---\nname: git:analyze-issue\ndescription: Analyze a GitHub issue and create a detailed technical specification\nargument-hint: Issue number (e.g., 42)\nallowed-tools: Bash(gh issue:*), Read, Write, Glob, Grep\n---\n\nPlease analyze GitHub issue #$ARGUMENTS and create a technical specification.\n\nFollow these steps:\n\n1. Check if the issue is already loaded:\n   - Look for the issue file in `.\u002Fspecs\u002Fissues\u002F` folder\n   - File naming pattern: `\u003Cnumber-padded-to-3-digits>-\u003Ckebab-case-title>.md`\n   - If not found, fetch the issue details from GitHub (see step 2)\n\n2. Fetch the issue details (if not already loaded):\n   - Read `.claude\u002Fcommands\u002Fload-issues.md` to understand how to fetch issue details\n   - Save the issue file following the load-issues.md format\n\n3. Understand the requirements thoroughly\n4. Review related code and project structure\n5. Create a technical specification with the format below\n\n# Technical Specification for Issue #$ARGUMENTS\n\n## Issue Summary\n- Title: [Issue title from GitHub]\n- Description: [Brief description from issue]\n- Labels: [Labels from issue]\n- Priority: [High\u002FMedium\u002FLow based on issue content]\n\n## Problem Statement\n[1-2 paragraphs explaining the problem]\n\n## Technical Approach\n[Detailed technical approach]\n\n## Implementation Plan\n1. [Step 1]\n2. [Step 2]\n3. [Step 3]\n\n## Test Plan\n1. Unit Tests:\n   - [test scenario]\n2. Component Tests:\n   - [test scenario]\n3. Integration Tests:\n   - [test scenario]\n\n## Files to Modify\n- [file path]: [changes]\n\n## Files to Create\n- [file path]: [purpose]\n\n## Existing Utilities to Leverage\n- [utility name\u002Fpath]: [purpose]\n\n## Success Criteria\n- [ ] [criterion 1]\n- [ ] [criterion 2]\n\n## Out of Scope\n- [item 1]\n- [item 2]\n\nRemember to follow our strict TDD principles, KISS approach, and 300-line file limit.\n\nIMPORTANT: After completing your analysis, SAVE the full technical specification to:\n`.\u002Fspecs\u002Fissues\u002F\u003Cnumber-padded-to-3-digits>-\u003Ckebab-case-title>.specs.md`\n\nFor example, for issue #7 with title \"Make code review trigger on any *.SQL and .sh file changes\", save to:\n`.\u002Fspecs\u002Fissues\u002F007-make-code-review-trigger-on-sql-sh-changes.specs.md`\n\nAfter saving, provide a brief summary to the user confirming:\n- Issue number and title analyzed\n- File path where the specification was saved\n- Key highlights from the specification (2-3 bullet points)\n","Please analyze GitHub issue #$ARGUMENTS and create a technical specification.\n\nFollow these steps:\n\n1. Check if the issue is already loaded:\n   - Look for the issue file in `.\u002Fspecs\u002Fissues\u002F` folder\n   - File naming pattern: `\u003Cnumber-padded-to-3-digits>-\u003Ckebab-case-title>.md`\n   - If not found, fetch the issue details from GitHub (see step 2)\n\n2. Fetch the issue details (if not already loaded):\n   - Read `.claude\u002Fcommands\u002Fload-issues.md` to understand how to fetch issue details\n   - Save the issue file following the load-issues.md format\n\n3. Understand the requirements thoroughly\n4. Review related code and project structure\n5. Create a technical specification with the format below\n\n# Technical Specification for Issue #$ARGUMENTS\n\n## Issue Summary\n- Title: [Issue title from GitHub]\n- Description: [Brief description from issue]\n- Labels: [Labels from issue]\n- Priority: [High\u002FMedium\u002FLow based on issue content]\n\n## Problem Statement\n[1-2 paragraphs explaining the problem]\n\n## Technical Approach\n[Detailed technical approach]\n\n## Implementation Plan\n1. [Step 1]\n2. [Step 2]\n3. [Step 3]\n\n## Test Plan\n1. Unit Tests:\n   - [test scenario]\n2. Component Tests:\n   - [test scenario]\n3. Integration Tests:\n   - [test scenario]\n\n## Files to Modify\n- [file path]: [changes]\n\n## Files to Create\n- [file path]: [purpose]\n\n## Existing Utilities to Leverage\n- [utility name\u002Fpath]: [purpose]\n\n## Success Criteria\n- [ ] [criterion 1]\n- [ ] [criterion 2]\n\n## Out of Scope\n- [item 1]\n- [item 2]\n\nRemember to follow our strict TDD principles, KISS approach, and 300-line file limit.\n\nIMPORTANT: After completing your analysis, SAVE the full technical specification to:\n`.\u002Fspecs\u002Fissues\u002F\u003Cnumber-padded-to-3-digits>-\u003Ckebab-case-title>.specs.md`\n\nFor example, for issue #7 with title \"Make code review trigger on any *.SQL and .sh file changes\", save to:\n`.\u002Fspecs\u002Fissues\u002F007-make-code-review-trigger-on-sql-sh-changes.specs.md`\n\nAfter saving, provide a brief summary to the user confirming:\n- Issue number and title analyzed\n- File path where the specification was saved\n- Key highlights from the specification (2-3 bullet points)\n",{"name":5,"description":7,"allowed-tools":39,"argument-hint":40},"Bash(gh issue:*), Read, Write, Glob, Grep","Issue number (e.g., 42)","master","c73386b305dec167db7654e0e6feacb462d4f9dc","assets\u002Fskills\u002Fdev\u002Fanalyze-issue",1,"https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code","https:\u002F\u002Fgithub.com\u002FAntifragileTech","2026-10-02 14:22:14",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add AntifragileTech\u002Fantifragile-claude-code --skill \"git:analyze-issue\"",{"tool":54,"command":55},"bunx","bunx skills add AntifragileTech\u002Fantifragile-claude-code --skill \"git:analyze-issue\"",{"tool":57,"command":58},"pnpm","pnpm dlx skills add AntifragileTech\u002Fantifragile-claude-code --skill \"git:analyze-issue\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fdev\u002Fanalyze-issue\u002FSKILL.md",true,[],[63,89,104,117,129,142],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":82,"publishedAt":34},"01M6DT9Q6VYA615SCXR757TZZ7","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fwriting-skills\u002FSKILL.md",[69,74,77],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":75,"categoryName":76,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[83,84,85,86,87,88],"writing skills","writing","use","editing","work","deployment",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":97,"publishedAt":34},"01M6DT9GFHDNY90P41WGAE1TV0","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fwriting-plans\u002FSKILL.md",[95,96],{"categoryNo":75,"categoryName":76,"taxonomyType":72,"taxonomyTypeDesc":73},{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[98,99,84,100,101,85,102,103],"plans","writing plans","requirements","task","code","spec",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":112,"publishedAt":34},"01M6DT9C6PFGD86WS3HY7YE3XG","docs:write-concisely","Apply writing rules to any documentation that humans will read. Makes your writing clearer, stronger, and more professional.","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fwrite-concisely\u002FSKILL.md",[110,111],{"categoryNo":75,"categoryName":76,"taxonomyType":72,"taxonomyTypeDesc":73},{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[113,31,114,30,115,116,84],"docs:write concisely","docs","Rules","documentation",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":34},"01M6DT98AWQ27P0N1CG97WAG66","kaizen:why","Iterative Five Whys root cause analysis drilling from symptoms to fundamentals","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fwhy\u002FSKILL.md",[],[119,124,125,21,126,127,128],"why","kaizen","five whys","analysis","root cause analysis",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":34},"01M6DT93EH25NAX19R3WGE1P53","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fverification-loop\u002FSKILL.md",[],[136,137,138,139,102,140,141],"verification loop","verification","loop","sessions","claude code sessions","system",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":34},"01M6DT90GW7Z7VCN98P9DVYSNC","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fverification-before-completion\u002FSKILL.md",[],[149,137,150,87,85,151,152,153],"verification before completion","commands","evidence","claim","complete"]