create-issue
Quickly capture bugs, features, or improvements as complete issues during development
Install
npx skillscat add jforksy/claude-skills/create-issue Install via the SkillsCat registry.
The create-issue skill lets a developer quickly turn a bug, feature idea, or improvement into a fully formatted issue while staying in the development flow. It solves losing ideas or delaying documentation by capturing title, description, files, and labels in one step. Use it mid‑development when you notice something that needs to be recorded.
Create Issue
User is mid-development and thought of a bug/feature/improvement. Capture it fast so they can keep working.
Your Goal
Create a complete issue with:
- Clear title
- TL;DR of what this is about
- Current state vs expected outcome
- Relevant files that need touching
- Risk/notes if applicable
- Proper type/priority/effort labels
How to Get There
Ask questions to fill gaps - be concise, respect the user's time. They're mid-flow and want to capture this quickly. Usually need:
- What's the issue/feature
- Current behavior vs desired behavior
- Type (bug/feature/improvement) and priority if not obvious
Keep questions brief. One message with 2-3 targeted questions beats multiple back-and-forths.
Search for context only when helpful:
- Web search for best practices if it's a complex feature
- Grep codebase to find relevant files
- Note any risks or dependencies you spot
Skip what's obvious - If it's a straightforward bug, don't search web. If type/priority is clear from description, don't ask.
Keep it fast - Total exchange under 2min. Be conversational but brief. Get what you need, create ticket, done.
Behavior Rules
- Be conversational - ask what makes sense, not a checklist
- Default priority: normal, effort: medium (ask only if unclear)
- Max 3 files in context - most relevant only
- Bullet points over paragraphs
Install
npx skillscat add jforksy/claude-skills/create-issue Install via the SkillsCat registry.