github-issues

Generate standardized GitHub issue templates with gh CLI commands and severity classification.

18|1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/kid-sid/codex-spellbook --skill github-issues-kid-sid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/kid-sid/codex-spellbook/tree/main/skills/github-issues
Command: npx skills add https://github.com/kid-sid/codex-spellbook --skill github-issues-kid-sid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Poorly written GitHub issues are frequently ignored, misrouted, or reopened for missing critical information, creating unnecessary friction for engineering teams and delaying bug fixes, feature delivery, and maintenance work.

Core Features & Use Cases

  • Standardized Issue Templates: Pre-built structures for bug reports, feature requests, regressions, flaky tests, security vulnerabilities, and performance issues that ensure all required context is included upfront.
  • gh CLI Integration: Ready-to-use command references for creating, editing, labeling, and managing issues programmatically, including bulk operations and cross-repo issue linking.
  • Triage & Classification Guidance: Clear severity/priority matrices, label definitions, and edge case handling rules for regressions, data-loss bugs, cross-platform issues, and duplicate detection to streamline issue triage.
  • Use Case Example: If your team regularly receives bug reports with no reproduction steps, this skill ensures every issue includes numbered repro steps, environment details, and acceptance criteria so engineers can start fixing immediately without follow-up requests.

Quick Start

Use the github-issues skill to file a complete bug report for the payment card decline issue with all required reproduction steps, environment details, and P1 severity classification.

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I write GitHub issues that engineers can actually resolve without follow-up questions?

To write actionable GitHub issues, use standardized templates that enforce numbered reproduction steps, environment details, and acceptance criteria upfront. This ensures bugs and feature requests include all required context for immediate engineering action.

What's the best way to automate GitHub issue creation and triage using the gh CLI?

Automate GitHub issue creation and triage by using gh CLI command references for creating, editing, labeling, and managing issues programmatically, including bulk operations and cross-repo issue linking for streamlined workflows.

How do I classify bug severity and priority during GitHub issue triage?

Classify bug severity and priority during GitHub issue triage by applying predefined severity and priority matrices, label definitions, and edge case handling rules for data-loss bugs and cross-platform issues.

Does this approach support documenting flaky tests and filing private security advisories?

Yes, this approach supports documenting flaky tests and filing private security advisories. It provides pre-built structures for security vulnerabilities, regressions, and flaky tests to ensure complete, properly labeled documentation.

How should I handle regression management and duplicate detection in GitHub issue tracking?

Handle regression management and duplicate detection in GitHub issue tracking by following standardized edge case handling rules and classification guidance, ensuring regressions and cross-repo issues are properly labeled and linked.