issue-creation

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

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill issue-creation-zmynxx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-creation
Source: https://github.com/zMynxx/bifrost-with-opencode/tree/main/.opencode/skills/issue-creation
Command: npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill issue-creation-zmynxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributors often file incomplete or duplicate GitHub issues, and maintainers lack a consistent triage process. This Skill enforces a structured issue-first workflow with mandatory templates, automatic labels, and a maintainer approval gate before any PR can be opened. ## Core Features & Use Cases - Template-driven issue creation: Guides users through the Bug Report and Feature Request templates with all required fields, pre-flight checkboxes, and correct formatting. - Label and approval workflow: Applies the status:needs-review / status:approved lifecycle so maintainers control which issues become actionable. - Duplicate prevention and triage: Searches existing issues first and routes questions to Discussions instead of the issue tracker. - Use Case: A contributor hits a zsh glob error in setup.sh. The Skill searches for duplicates, drafts a complete bug report via gh issue create --template bug_report.yml, and the issue lands with bug and status:needs-review labels awaiting maintainer approval. ## Quick Start Create a GitHub bug report issue for the setup script failing on zsh, following the repository's issue template and approval workflow.

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 the GitHub CLI with gh issue create and a template flag, such as gh issue create --template "bug_report.yml" --title "fix(scope): description". Fill in all required template fields in the body, including pre-flight checkboxes.

How do I write a good bug report for a GitHub project?▼

A good bug report includes a clear description, numbered steps to reproduce, expected versus actual behavior, and environment details like OS, agent client, and shell. Search existing issues first to avoid duplicates.

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

No. Every new issue receives the status:needs-review label automatically, and a maintainer must add status:approved before any linked PR can be opened. This keeps the backlog scoped and reviewed.

Where should I ask questions instead of opening a GitHub issue?▼

Questions belong in GitHub Discussions, not the issue tracker. Issues are reserved for actionable bug reports and feature requests that follow the repository templates.

Why was my GitHub issue closed or not approved?▼

Issues are typically rejected for being duplicates, out of scope, unclear, or submitted as questions rather than bugs or features. Maintainers comment with the reason and may close the issue during review.