issue-creation

Create GitHub issues with required templates and status:needs-review.

2|Updated Jul 29, 2025
One-click install
npx skills add https://github.com/kurojs/EnderDots --skill issue-creation-kurojs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-creation
Source: https://github.com/kurojs/EnderDots/tree/main/.config/opencode/skills/issue-creation
Command: npx skills add https://github.com/kurojs/EnderDots --skill issue-creation-kurojs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you create high-quality GitHub issues that follow the repo’s required templates and approval workflow, reducing back-and-forth with maintainers.

Core Features & Use Cases

  • Duplicate-first issue creation: Searches existing issues before you write a new one to avoid repeats.
  • Template-correct bug/feature reporting: Selects the proper Bug Report or Feature Request template and fills required fields.
  • Enforced maintainer review pipeline: Ensures every created issue starts with status:needs-review and routes questions to Discussions instead of issues.

Quick Start

Use the skill to create a bug report issue by ensuring you’ve reviewed existing issues and populated all required bug-report fields.

Frequently Asked Questions about issue-creation

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

FAQPage Schema
How do I create GitHub issues that follow template requirements automatically?

To avoid duplicate GitHub issues, this skill searches existing issues before creating a new one. This duplicate-first detection workflow prevents repeats and reduces back-and-forth with maintainers during the triage process.

When should I use GitHub Discussions instead of creating a new issue?

You should use GitHub Discussions instead of creating an issue when asking questions. This skill identifies question-type inquiries and routes them to Discussions automatically, keeping the issue tracker reserved for actionable bug reports and feature requests.

Does creating a GitHub issue require maintainer approval before opening a pull request?

Yes, creating a GitHub issue requires maintainer approval before opening any pull request. This skill enforces a review pipeline where new issues start with status:needs-review and require status:approved before PR creation begins.

What is the triage workflow for maintaining status labels on GitHub issues?

The triage workflow for GitHub issues involves applying status labels like status:needs-review upon creation and status:approved after maintainer review. This skill automates label application to maintain a clean, approval-ready pipeline.