
Create Github Issue
Create GitHub issues using GitHub CLI with support for templates, labels, assignees...
Install
npx skills add tailcallhq/forgecode --skill create-github-issue -g -a claude-code -y- Repository
- tailcallhq/forgecode7.6k
- Category
- Git and review
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Lightabout 956 tokens
- Runs scripts
- No, instructions only
What it does
Create GitHub issues using GitHub CLI with support for templates, labels, assignees, milestones, and draft issues. Use when the user asks to create a GitHub issue, file a bug report, submit a feature request, or open an issue in a GitHub repository.
Create GitHub Issue
Create comprehensive GitHub issues using gh issue create by dynamically discovering and adhering to the repository's official issue templates.
Workflow
1. Discover and Select Template
CRITICAL: You must use the repository's official templates. Do not assume the structure.
- List available templates:
ls .github/ISSUE_TEMPLATE/ - Select the most appropriate template based on the issue type (e.g.,
bug_report.yml,feature_request.yml). - Read the selected template to understand its required fields, structure, and any title prefixes or default labels.
cat .github/ISSUE_TEMPLATE/<selected_template>.yml
2. Gather Context
Gather relevant information to fulfill the template requirements:
# Check current git status for context
git status
# View recent commits if related to codebase changes
git log --oneline -10
# Check if related issues exist
gh issue list --search "keyword" --limit 10
3. Generate Markdown Body
MANDATORY: Structure the issue body exactly as defined in the selected YAML template without exception.
- Map YAML fields to Markdown: Convert each field in the template (typically found under
body:) into a Markdown section. - Use Headers: Use the
labeloridfrom the YAML field as an H2 header (e.g.,## Bug Description). - Respect Validation: Ensure all fields marked as
required: truein the YAML are populated with meaningful content. - Format Correctly: Use code blocks (e.g.,
```shell,```yaml) for logs and configurations as suggested by the template'srenderattribute.
4. Choose Labels
Select labels by inspecting .github/labels.json.

