analyze-issue
Analyze a GitHub issue and create detailed analysis in workflows/
npx skills add majiayu000/claude-skill-registry --skill analyze-issue-gittower-git-flow-next-a94006a1 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Analyze Issue Perform detailed analysis of a GitHub issue and write the analysis to the workflows directory. ## Instructions 1. **Fetch Issue Details** - Get issue #$ARGUMENTS from gittower/git-flow-next - Extract: title, description, labels, any linked issues 2. **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/` 3. **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 4. **Write Analysis Document** - Create `analysis.md` in the workflow folder - Use the template below 5. **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`: ```markdown # Issue #<number>: <title> ## Summary <1-2 sentence summary of the issue> ## Issue Details - **Type**: <bug/enhancement/feature> - **Labels**: <labels from GitHub> - **Link
- Instructions
- Analysis Template
What does the analyze-issue skill do?
Analyze a GitHub issue and create detailed analysis in workflows/
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill analyze-issue-gittower-git-flow-next-a94006a1 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.