issue-creation

Creates GitHub issues using bug report and feature request templates with label workflows.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/albersg/dotfiles --skill issue-creation-albersg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-creation
Source: https://github.com/albersg/dotfiles/tree/main/dotfiles-opencode/.opencode/skills/issue-creation
Command: npx skills add https://github.com/albersg/dotfiles --skill issue-creation-albersg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Filing GitHub issues often leads to duplicates, missing information, or bypassed review processes. This Skill enforces a structured issue-first workflow so every bug report or feature request follows the correct template, includes all required fields, and respects the maintainer approval process before any PR is opened. ## Core Features & Use Cases - Template-Guided Issue Creation: Uses the repository's bug report and feature request templates with all required fields, including pre-flight checks, reproduction steps, and environment details. - Label and Approval Workflow: Applies the status:needs-review and status:approved label lifecycle so maintainers control which issues become eligible for pull requests. - Duplicate Prevention: Searches existing issues with gh CLI before creating new ones and routes questions to Discussions instead of issues. - Use Case: A contributor hits a zsh glob error in setup.sh. The Skill searches for duplicates, drafts a complete bug report with reproduction steps and logs, and submits it via gh issue create with the correct template. ## Quick Start Create a GitHub bug report for the setup.sh zsh glob error using the bug report template with full reproduction steps.

Frequently Asked Questions about issue-creation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitHub issue from the command line?▼

Use gh issue create with the --template flag to select bug_report.yml or feature_request.yml, plus --title and --body for content. Search existing issues first with gh issue list --search to avoid duplicates.

What is the difference between a bug report and feature request template?▼

Bug reports require reproduction steps, expected versus actual behavior, OS, agent, and shell details, and get the bug label. Feature requests require a problem description, proposed solution, and affected area, and get the enhancement label.

Can I open a pull request before my issue is approved?▼

No. Every new issue receives status:needs-review automatically, and a maintainer must add status:approved before any linked PR can be opened. This keeps contributions aligned with project scope.

Where should I ask questions instead of opening an issue?▼

Questions belong in GitHub Discussions, not issues. Issues are reserved for confirmed bugs and feature requests, and blank issues are disabled so a template is always required.

Why was my GitHub issue closed as a duplicate?▼

Issues are closed as duplicates when an existing issue covers the same problem. Run gh issue list --search with relevant keywords before creating a new issue and link to the existing one instead.