| name | analyze-issue |
| description | Analyze a GitHub issue and create detailed analysis in workflows/ |
| argument-hint | <issue-number> |
| allowed-tools | Read, Grep, Glob, Write, Bash, mcp__github__get_issue |
| context | fork |
| agent | Explore |
Analyze Issue
Perform detailed analysis of a GitHub issue and write the analysis to the workflows directory.
Instructions
-
Fetch Issue Details
- Get issue #$ARGUMENTS from gittower/git-flow-next
- Extract: title, description, labels, any linked issues
-
Create Workflow Directory
- Create
workflows/issue-<number>-<slug>/
- Slug: lowercase, hyphenated version of key words from title (max 4 words)
- Example: Issue #42 "Add squash merge support" →
workflows/issue-42-squash-merge/
-
Explore the Codebase
- Search for related code, files, and patterns
- Identify affected components
- Understand current implementation
- Find similar patterns or prior art in the codebase
-
Write Analysis Document
- Create
analysis.md in the workflow folder
- Use the template below
-
Propose TODO Comments
- If specific code locations need attention, suggest TODO comments
- Format:
// TODO(#<issue>): <description>
Analysis Template
Write to workflows/issue-<number>-<slug>/analysis.md:
# Issue #<number>: <title>
## Summary
<1-2 sentence summary of the issue>
## Issue Details
- **Type**: <bug/enhancement/feature>
- **Labels**: <labels from GitHub>
- **Link**: <GitHub issue URL>
## Analysis
### Understanding
<What is being requested/reported? Clarify any ambiguity>
### Root Cause (for bugs)
<What's causing this behavior? Include file:line references>
### Affected Components
List all files/packages that will need changes:
- `cmd/<file>.go` - <why this file is affected>
- `internal/<package>/<file>.go` - <why>
### Current Behavior
<How does the ?>
Based on TESTING
- Report Completion
- Show path to created analysis file
- Summarize key findings
- Suggest next step: create feature branch and run
/create-plan