/issue - Issue Creation Skill

Create GitHub Issues with consistent formatting and sufficient technical detail for autonomous implementation.

Language Requirement

IMPORTANT: All GitHub Issues MUST be written in English.

• Issue title: English
• Issue body: English
• Labels: English
• Comments: English

Steps

1. Read Issue Guidelines (MANDATORY)

Before drafting any Issue content, read:

• .claude/issue-guidelines.md — full Issue creation guidelines, templates, and quality checklist

This file contains the authoritative structure, Pre-Submission Verification checklist, and examples of good/bad Issues.

2. Gather Information

After reading the guidelines, gather the following information from the user:

• Type: Feature, Bug, Documentation, Refactor, or other
• Summary: Brief description of the task
• Context: Why is this needed?
• Technical Details: Implementation hints if available

2. Determine Issue Template

Based on the type, use the appropriate structure:

Feature Request

markdown
1## Summary
2[Brief description of the feature]
3
4## Problem
5[What problem does this solve?]
6
7## Proposed Solution
8[How should this be implemented?]
9
10## Technical Implementation
11[Technical details for autonomous implementation]
12- Files to modify:
13- New files to create:
14- Dependencies:
15- Architecture considerations:
16
17## Acceptance Criteria
18- [ ] [Specific, testable criterion]
19- [ ] [Another criterion]
20- [ ] Tests added
21- [ ] Documentation updated (if applicable)

Bug Report

markdown
1## Summary
2[Brief description of the bug]
3
4## Current Behavior
5[What happens now?]
6
7## Expected Behavior
8[What should happen?]
9
10## Steps to Reproduce
111. [Step 1]
122. [Step 2]
133. [Step 3]
14
15## Technical Details
16- Environment: [OS, Rust version, etc.]
17- Error messages:
18- Related files:
19
20## Proposed Fix
21[Technical approach to fix]
22
23## Acceptance Criteria
24- [ ] Bug is fixed
25- [ ] Tests added to prevent regression
26- [ ] No new warnings from clippy

3. Validate Completeness

Before creating the Issue, verify:

• Title is concise and descriptive (in English)
• Technical detail is sufficient for autonomous implementation
• Acceptance criteria are specific and testable
• Labels are appropriate (bug, enhancement, documentation, etc.)
• Related Issues/PRs are referenced if applicable

4. Create the Issue

Use the gh CLI to create the Issue:

bash
1gh issue create --title "TITLE" --body "BODY" --label "LABEL"

5. Confirm Creation

After creating, output:

• Issue URL
• Issue number
• Summary of what was created

Labels Reference

Common labels for this project:

• bug - Bug fixes
• enhancement - New features or improvements
• documentation - Documentation updates
• refactor - Code refactoring
• security - Security-related issues
• performance - Performance improvements
• testing - Test additions or improvements

Example Usage

User: "バグ報告したい。cargo run で --no-network オプションが効かない"

Claude executes /issue skill:

1. Gathers details about the bug
2. Creates English Issue with proper template
3. Adds bug label
4. Creates Issue using gh issue create
5. Reports Issue URL to user