issue-creation

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

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Balthael/ciberbal-ai --skill issue-creation-balthael
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-creation
Source: https://github.com/Balthael/ciberbal-ai/tree/main/internal/assets/skills/issue-creation
Command: npx skills add https://github.com/Balthael/ciberbal-ai --skill issue-creation-balthael

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Filing GitHub issues without structure leads to incomplete bug reports, duplicate submissions, and unreviewed feature requests. This Skill enforces an issue-first workflow where every issue uses a template, receives automatic triage labels, and requires maintainer approval before any pull request can be opened. ## Core Features & Use Cases - Template-Based Issue Creation: Guides contributors through the 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 label on creation and explains the maintainer approval process using status:approved and priority labels. - CLI Command Reference: Provides ready-to-use gh CLI commands for searching duplicates, creating issues, and managing labels. - Use Case: A contributor discovers that a setup script fails on zsh. Use this Skill to search for duplicates, file a structured bug report via gh issue create with the bug_report.yml template, and wait for maintainer approval before opening a PR. ## Quick Start Create a GitHub bug report issue for the zsh glob error in setup.sh using the bug report template and the gh CLI.

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 gh CLI with gh issue create, passing a template and title. For example, gh issue create --template "bug_report.yml" --title "fix(scripts): description" creates a structured bug report with auto-applied labels.

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 automatically to new GitHub issues?

Bug reports receive the bug and status:needs-review labels, while feature requests receive 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. The workflow requires a maintainer to add the status:approved label to an issue before any linked pull request can be opened. This ensures all work is scoped and reviewed in advance.

Where should questions go instead of GitHub issues?

Questions belong in GitHub Discussions, not issues. The issue tracker is reserved for bug reports and feature requests submitted through the official templates, since blank issues are disabled.