issue-creation

Enforce GitHub issue creation with required templates and status labels.

Updated Mar 30, 2026

Search Tags:#workflow #templates #github #labels #feature-request #issue-triage #bug-report

Ready to run

npx skills add https://github.com/dtaborda/startup-saas-template --skill issue-creation-dtaborda

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-creation
Source: https://github.com/dtaborda/startup-saas-template/tree/main/skills/issue-creation
Command: npx skills add https://github.com/dtaborda/startup-saas-template --skill issue-creation-dtaborda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures GitHub issues are never blank, always use the right template, and wait for maintainer approval so every report is actionable and triage-ready.

Core Features & Use Cases

Template enforcement: Contributors must pick either the bug_report.yml or feature_request.yml template and answer all required fields before submitting an issue.
Label and status workflow: Every new issue gains labels like bug or enhancement plus status:needs-review, and maintainers add status:approved once the issue passes validation.
Use Case: When a contributor reports a setup script failure, guide them to select the bug report template, capture OS/agent/shell info, and wait for approval before linking a PR.

Quick Start

When triaging or filing a bug, ask the agent to create a GitHub issue with the proper template, complete every required field, and wait for a maintainer to add status:approved.

Frequently Asked Questions about issue-creation

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

FAQPage Schema

How do I enforce structured GitHub issue creation workflows for contributors?▼

Enforce structured GitHub issue creation by guiding contributors to use specific bug_report.yml or feature_request.yml templates, complete required fields, and apply automatic status:needs-review labels before submission.

What is the GitHub issue triage process for bug reports and feature requests?▼

The GitHub issue triage process requires contributors to file reports using bug_report.yml or feature_request.yml templates with appropriate labels. Issues receive status:needs-review initially, then maintainers apply status:approved after validation passes.

How do I require template usage and pre-flight checkbox completion for GitHub issues?▼

Require template usage by enforcing contributors to choose between bug_report.yml and feature_request.yml formats. The workflow demands all required fields and pre-flight checkboxes are completed before an issue can be successfully submitted.

Can I use GitHub issue templates to require maintainer approval before opening a pull request?▼

Yes, GitHub issue templates can enforce a workflow where issues receive status:needs-review upon creation, and maintainers must apply status:approved after validation. Contributors wait for this approval before opening any linked pull request.

What labels should I use for GitHub issue triage and status tracking?▼

Use bug or enhancement labels to categorize new GitHub issues, alongside status:needs-review for initial triage tracking. Maintain apply status:approved once the issue passes validation and is ready for pull request linkage.

Why do my GitHub issues lack consistent formatting and actionable details?▼

GitHub issues lack consistency when contributors skip templates. Enforce structured workflows requiring bug_report.yml or feature_request.yml templates to capture OS, agent, and shell info, ensuring every report is actionable and triage-ready.