Stats
Actions
Tags
From issue
Refines brief bug, feature, or refactor descriptions into structured issues with technical context, code links, and details for developers and AI agents.
How this skill is triggered — by the user, by Claude, or both
Slash command
/issue:refineThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Expand brief issue descriptions into structured issues for developers and AI agents.
Expand brief issue descriptions into structured issues for developers and AI agents.
| Type | When to Use | Guide |
|---|---|---|
| Bug | Something is broken | bug.md |
| Feature | New capability | feature.md |
| Refactor | Internal improvement, no behavior change | refactor.md |
All issues share this skeleton. Type guides add sections in between.
## Summary
One to two sentences.
[Type-specific sections from guide]
## Context
### Related Code
Files that need changes or inform the work.
### Related Issues
Links to related issues, prior attempts, upstream work.
https://github.com/{owner}/{repo}/blob/{sha}/path#L10-L20), file paths elsewhere (path/to/file:10-20)Fetch with get_issue, output refinement for review, update only after approval.
mcp__linear__get_issue, mcp__linear__update_issue, or mcp__claude_ai_Linear__get_issue, mcp__claude_ai_Linear__save_issuemcp__github__get_issue, mcp__github__update_issuenpx claudepluginhub bendrucker/claude --plugin issueUpdates GitHub issue descriptions with structured analysis (summary, requirements, references, implementation plan, impact scope) based on issue number, request, code, docs, and designs.
Investigates and resolves GitHub issues with systematic triage, root cause analysis, test-driven fixes, and pull request management. Use when given an issue ID or URL.
Manages full GitHub issue lifecycle: create with conventional commit titles, sub-issues, cross-repo links, edit/view/list, dump trees to markdown/YAML, push from files, comment/label/close.