issue-creation

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

Updated May 24, 2026
One-click install
npx skills add https://github.com/etrigan16/v0-cipher-ar --skill issue-creation-etrigan16
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-creation
Source: https://github.com/etrigan16/v0-cipher-ar/tree/main/.opencode/skills/issue-creation
Command: npx skills add https://github.com/etrigan16/v0-cipher-ar --skill issue-creation-etrigan16

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 workflow with automatic labeling and maintainer approval gates. ## Core Features & Use Cases - Template-Based Issue Creation: Guides bug reports and feature requests through required fields like reproduction steps, environment details, and pre-flight duplicate checks. - Label Workflow Enforcement: Applies status:needs-review automatically and requires maintainer status:approved before any PR can be opened. - CLI Command Reference: Provides ready-to-use gh issue create, search, and label commands for contributors and maintainers. - Use Case: A contributor hits a zsh glob error in setup.sh, searches for duplicates, files a bug report via the template with OS, shell, and logs, and waits for maintainer approval before opening a fix PR. ## 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 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. Questions should go to Discussions instead of issues.

How do maintainers approve and prioritize GitHub issues?▼

Maintainers run gh issue edit <number> --add-label status:approved to accept an issue for implementation. They can also add priority:high, priority:medium, or priority:low labels to indicate urgency.

When should I use Discussions instead of GitHub issues?▼

Use Discussions for questions rather than bugs or feature proposals. Issues are reserved for actionable bug reports and feature requests; duplicates should be linked to the existing issue and closed.