Issue Creation Skill

Create an issue that follows project templates and conventions.

When to Use

• •User wants to report a bug
• •User wants to request a feature
• •User has a question about the project
• •User says "create issue" or "file issue"

Process

1. •

   Check for duplicates

   • •Search existing issues via GitHub MCP
   • •Look for similar titles and content
   • •Suggest commenting on existing if duplicate
2. •

   Load project template

   • •Check .github/ISSUE_TEMPLATE/
   • •Use appropriate template (bug, feature, question)
   • •Fall back to standard format if none
3. •

   Fill template

   • •Prompt user for required fields
   • •Format according to project style
   • •Add appropriate labels suggestion

Output Format

Respond in user's language:

# Issue Creation

## Duplicate Check
**Searched**: [search terms]
**Similar issues found**:
- #[number]: [title] - [status]

**Recommendation**: [Proceed / Comment on existing]

---

## Issue Type
[Bug Report / Feature Request / Question]

## Title

[Template-compliant title]

## Body
```markdown
## Description
[Clear description]

## For Bug Reports:
### Environment
- OS: 
- Version:

### Steps to Reproduce
1. 
2. 
3. 

### Expected Behavior
[What should happen]

### Actual Behavior
[What happens]

## For Feature Requests:
### Problem
[What problem does this solve]

### Proposed Solution
[How should it work]

### Alternatives
[Other approaches considered]

Suggested Labels

• •bug / enhancement / question
• •[component label if applicable]

## Arguments

`$ARGUMENTS` can include:
- Type: `bug`, `feature`, `question`, `docs`
- Repository: `owner/repo`