analyze-issue
Analyze a GitHub issue and create a detailed technical specification
它会碰到什么
这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。
技能内容
Please analyze GitHub issue #$ARGUMENTS and create a technical specification.
Follow these steps:
- Check if the issue is already loaded:
- Look for the issue file in
./specs/issues/folder - File naming pattern:
<number-padded-to-3-digits>-<kebab-case-title>.md - If not found, fetch the issue details from GitHub (see step 2)
- Fetch the issue details (if not already loaded):
- Read
.claude/commands/load-issues.mdto understand how to fetch issue details - Save the issue file following the load-issues.md format
- Understand the requirements thoroughly
- Review related code and project structure
- Create a technical specification with the format below
Technical Specification for Issue #$ARGUMENTS
Issue Summary
- Title: [Issue title from GitHub]
- Description: [Brief description from issue]
- Labels: [Labels from issue]
- Priority: [High/Medium/Low based on issue content]
Problem Statement
[1-2 paragraphs explaining the problem]
Technical Approach
[Detailed technical approach]
Implementation Plan
- [Step 1]
- [Step 2]
- [Step 3]
Test Plan
- Unit Tests:
- [test scenario]
- Component Tests:
- [test scenario]
- Integration Tests:
- [test scenario]
Files to Modify
- [file path]: [changes]
Files to Create
- [file path]: [purpose]
Existing Utilities to Leverage
- [utility name/path]: [purpose]
Success Criteria
- [ ] [criterion 1]
- [ ] [criterion 2]
Out of Scope
- [item 1]
- [item 2]
Remember to follow our strict TDD principles, KISS approach, and 300-line file limit.
IMPORTANT: After completing your analysis, SAVE the full technical specification to:
./specs/issues/<number-padded-to-3-digits>-<kebab-case-title>.specs.md
For example, for issue #7 with title "Make code review trigger on any *.SQL and .sh file changes", save to:
./specs/issues/007-make-code-review-trigger-on-sql-sh-changes.specs.md
After saving, provide a brief summary to the user confirming:
- Issue number and title analyzed
- File path where the specification was saved
- Key highlights from the specification (2-3 bullet points)
想直接用这个技能?
本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。
它属于哪个仓库
plugins/git/skills/analyze-issue/SKILL.md同一个仓库里的其他技能
同名技能的其他版本
有 3 个不同仓库或目录里都有叫 analyze-issue 的技能。它们内容并不相同,别混用:
- NeoLabHQ/context-engineering-kit — Analyze a GitHub issue and create a detailed technical specification
- NeoLabHQ/context-engineering-kit — Analyze a GitHub issue and create a detailed technical specification