creating-issues

Create GitHub issues (feature requests or bug reports) by learning from existing issue formats in the repository.

⭐5stars🔀0forks📁View on GitHub🕐Updated Dec 3, 2025

When & Why to Use This Skill

This Claude skill automates the creation of high-quality GitHub issues by analyzing and mimicking existing repository patterns. It streamlines the development workflow by ensuring all bug reports and feature requests adhere to project-specific formatting, labels, and structures while proactively identifying duplicates to maintain repository hygiene.

Use Cases

  • Standardized Bug Reporting: Automatically generate detailed bug reports that include reproduction steps, environment details, and expected behavior tailored to the specific repository's style.
  • Feature Request Alignment: Draft comprehensive enhancement proposals that match the project's preferred structure, tone, and level of detail to improve approval rates.
  • Duplicate Issue Prevention: Search and analyze existing issues before submission to prevent redundant entries and suggest engagement with existing threads.
  • Open Source Contribution: Assist external contributors in following complex project-specific issue templates and contribution guidelines without manual oversight.
  • Repository Maintenance: Quickly triage and document internal tasks or technical debt using the exact metadata and labeling conventions of the codebase.
name"Creating Issues"
description"Create GitHub issues (feature requests or bug reports) by learning from existing issue formats in the repository."

Creating Issues

Phase 1: Search Duplicates

1. Determine type:

  • Feature request: New functionality, enhancement
  • Bug report: Broken, not working, error

2. Search existing:

gh search issues --repo anthropics/claude-code "{key terms}" --limit 15

3. Check duplicates:

  • Show similar issues (titles, URLs)
  • View potential duplicates: gh issue view --repo anthropics/claude-code [number] --comments
  • Check if user engaged (commented, reacted)
  • Ask: "Do any match what you're reporting?"

4. If duplicate:

  • Not engaged: Offer +1 reaction/comment
    gh issue comment --repo anthropics/claude-code [number] --body "+1"
    
  • Already engaged: Note participation, end workflow

Phase 2: Learn Format

CRITICAL: Don't impose fixed template. Learn from repo.

1. Fetch similar issues:

# Feature requests
gh search issues --repo anthropics/claude-code "is:issue label:enhancement" --limit 5

# Bug reports
gh search issues --repo anthropics/claude-code "is:issue label:bug" --limit 5

2. Analyze structure:

gh issue view --repo anthropics/claude-code [number]

3. Identify patterns:

  • Sections used (Problem, Solution, Steps to Reproduce)
  • Detail level (brief vs comprehensive)
  • Checklists, code blocks, examples
  • Tone (formal vs casual)
  • Component tags

4. Extract template:

  • Consistent sections
  • Optional vs required
  • Markdown patterns

Phase 3: Draft Issue

1. Apply learned structure:

  • Match repository patterns
  • Match detail level
  • Use similar formatting
  • Adopt appropriate tone

2. Feature Request Structure (adapt):

## Problem / Use Case
[What trying to do or what's missing]

## Proposed Solution
[What to add or change]

## Example Usage
[Concrete example]

## Additional Context
[Optional: screenshots, related issues]

3. Bug Report Structure (adapt):

## Description
[What's happening vs should happen]

## Steps to Reproduce
1. [First]
2. [Second]
3. [Third]

## Expected / Actual Behavior
Expected: [what should happen]
Actual: [what happens]

## Environment
- Claude Code version: [version]
- OS: [OS]

## Additional Context
[Optional: errors, screenshots, logs]

4. Gather information:

  • Ask clarifying questions based on learned format
  • Request details from similar issues
  • Keep conversational

Phase 4: Preview & Refine

1. Show draft:

════════════════════════════════════════
📋 DRAFT ISSUE: [Type]
════════════════════════════════════════
🏷️  TITLE: [Clear, searchable title]

📝 BODY:
[Full content]

📊 METADATA:
- Type: [Feature/Bug]
- Labels: [Suggested]
- Similar: [Related issue numbers]
════════════════════════════════════════

2. Get feedback:

  • "Does this capture what you want?"
  • "Submit or adjust?"

3. Iterate if needed

Phase 5: Submit

1. Only with explicit approval ("yes", "submit", "go ahead")

2. Create:

gh issue create \
  --repo anthropics/claude-code \
  --title "[title]" \
  --body "$(cat <<'EOF'
[content]
EOF
)"

3. Confirm:

✅ Issue #[number]: [title]
🔗 URL: [URL]

View: gh issue view --repo anthropics/claude-code [number]

Advanced

Specific issue format:

gh issue view --repo anthropics/claude-code [reference-number]

Other repos:

gh search issues --repo [owner/repo] "{terms}"

Label suggestions:

gh label list --repo anthropics/claude-code
# Suggest: bug, enhancement, documentation, plugin, mcp, hooks

Best Practices

Feature Requests:

  • Start with "why"
  • Concrete examples
  • Open to alternatives
  • Link related issues
  • Consider scope

Bug Reports:

  • Exact steps
  • Include context (version, OS)
  • Actual vs expected
  • Evidence (errors, screenshots)
  • Minimal reproduction

General:

  • Clear, searchable titles
  • One issue per report
  • Search first
  • Be respectful
  • Follow up

Quick Reference

# Search
gh search issues --repo anthropics/claude-code "{terms}" --limit 15

# View
gh issue view --repo anthropics/claude-code [number] --comments

# Create
gh issue create --repo anthropics/claude-code --title "Title" --body "Body"

# Comment
gh issue comment --repo anthropics/claude-code [number] --body "+1"

# Labels
gh label list --repo anthropics/claude-code