issue-creation

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

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/AD-Paladins/beaconator-web --skill issue-creation-ad-paladins
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-creation
Source: https://github.com/AD-Paladins/beaconator-web/tree/main/.config/opencode/skills/issue-creation
Command: npx skills add https://github.com/AD-Paladins/beaconator-web --skill issue-creation-ad-paladins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Filing GitHub issues without structure leads to duplicates, missing reproduction details, and unreviewed PRs. This Skill enforces a template-driven issue creation process with duplicate checks, required fields, and a maintainer approval workflow. ## Core Features & Use Cases - Template-Based Issue Creation: Uses bug report and feature request templates with required fields like reproduction steps, environment details, and pre-flight checkboxes. - Label Workflow Automation: Applies status:needs-review automatically and guides maintainers to add status:approved before any PR is opened. - Duplicate Prevention: Searches existing issues with gh CLI before creating new ones and routes questions to Discussions instead. - Use Case: A contributor hits a zsh glob error in setup.sh, searches for duplicates, files a bug report via gh issue create with the bug_report.yml template, and waits for maintainer approval before opening a PR. ## Quick Start Ask the AI to create a GitHub bug report for the issue you encountered, including reproduction steps and your environment details.

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 a template flag, such as gh issue create --template "bug_report.yml" --title "fix(scope): description". Fill in all required fields like reproduction steps, expected behavior, and environment details in the body.

How do I check for duplicate GitHub issues before filing?▼

Run gh issue list --search "keyword" to search existing open and closed issues before creating a new one. If a duplicate exists, link to the original issue instead of filing a new one.

What labels are applied when creating a GitHub issue from a template?▼

Bug report templates automatically apply bug and status:needs-review labels, while feature request templates apply enhancement and status:needs-review. Maintainers later add status:approved and priority labels during triage.

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

No, a maintainer must add the status:approved label to the issue before any PR can be opened. This approval gate ensures issues are valid, clear, and in scope before implementation work begins.

When should I use GitHub Discussions instead of issues?▼

Use Discussions for questions rather than bug reports or feature requests. Issues are reserved for actionable bugs and enhancements, while general questions and conversations belong in the Discussions tab.