git:analyze-issue
Analyze a GitHub issue and create a detailed technical specification
Best use case
git:analyze-issue is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Analyze a GitHub issue and create a detailed technical specification
Teams using git:analyze-issue should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/analyze-issue/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How git:analyze-issue Compares
| Feature / Agent | git:analyze-issue | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Analyze a GitHub issue and create a detailed technical specification
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Please analyze GitHub issue #$ARGUMENTS and create a technical specification. Follow these steps: 1. 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) 2. Fetch the issue details (if not already loaded): - Read `.claude/commands/load-issues.md` to understand how to fetch issue details - Save the issue file following the load-issues.md format 3. Understand the requirements thoroughly 4. Review related code and project structure 5. 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 1. [Step 1] 2. [Step 2] 3. [Step 3] ## Test Plan 1. Unit Tests: - [test scenario] 2. Component Tests: - [test scenario] 3. 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)
Related Skills
token-integration-analyzer
Token integration and implementation analyzer based on Trail of Bits' token integration checklist. Analyzes token implementations for ERC20/ERC721 conformity, checks for 20+ weird token patterns, assesses contract composition and owner privileges, performs on-chain scarcity analysis, and evaluates how protocols handle non-standard tokens. Context-aware for both token implementations and token integrations.
entry-point-analyzer
Analyzes smart contract codebases to identify state-changing entry points for security auditing. Detects externally callable functions that modify state, categorizes them by access level (public, admin, role-restricted, contract-only), and generates structured audit reports. Excludes view/pure/read-only functions. Use when auditing smart contracts (Solidity, Vyper, Solana/Rust, Move, TON, CosmWasm) or when asked to find entry points, audit flows, external functions, access control patterns, or privileged operations.
my-issues
List my issues in the current repository
team-collaboration-issue
You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an
git:load-issues
Load all open issues from GitHub and save them as markdown files
github-issues
Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, or manage issue workflows. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", or any GitHub issue management task.
github-issue-creator
Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wan...
create-github-issues-for-unmet-specification-requirements
Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.
create-github-issues-feature-from-implementation-plan
Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.
terraform-azurerm-set-diff-analyzer
Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.
log-analyzer
全维度日志分析技能。自动识别日志类型（Java应用/MySQL Binlog/Nginx/Trace/告警），提取关键实体（IP、thread_id、trace_id、用户、表名等），进行根因定位、告警分析、异常洞察。支持100M+大文件。触发词：分析日志、日志排查、根因定位、告警分析、异常分析。
gen-specs-as-issues
This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.