issue

Creates and manages document bundlesGitHub issue bundles with configurable workflows.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/n0rvyn/indie-toolkit --skill issue-n0rvyn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/n0rvyn/indie-toolkit/tree/main/dev-workflow/skills/issue
Command: npx skills add https://github.com/n0rvyn/indie-toolkit --skill issue-n0rvyn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a single, consistent way to list, read, and create GitHub Issues from developer conversation, reducing context switching and ensuring bug reports include actionable prior hypotheses for faster debugging.

Core Features & Use Cases

  • List and Read Issues: Use the gh CLI to display open issues in a table and view issue details including title, state, labels, milestone, and body.
  • Create Issues with Prior Hypotheses: Classify the report, optionally validate referenced files, and generate 3–5 falsifiable prior hypotheses for bugs to include in the issue body; supports creating labels if missing.
  • Developer Triage Workflow: Ideal for capturing bugs, enhancements, or questions discovered during development and immediately linking them to a follow-up fix workflow such as running /fix-bug on a selected issue.

Quick Start

Create an issue describing a reproducible bug in the auth module with steps to reproduce and include prior hypotheses for diagnosis.

Frequently Asked Questions about issue

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

FAQPage Schema
How do I create GitHub issues with falsifiable prior hypotheses for bug tracking?

You can create GitHub issues with prior hypotheses by classifying the bug, validating referenced files, and generating 3–5 falsifiable hypotheses in the issue body for faster debugging.

Can I list and read GitHub issues using gh CLI for developer triage workflows?

Yes, listing and reading GitHub issues via gh CLI for developer triage displays open issues in a table and shows details including title, state, labels, milestone, and body for efficient bug tracking.

What is the best way to manage GitHub issue labels when creating new bug reports?

Managing GitHub issue labels during bug report creation verifies repository context and ensures labels exist, automatically creating missing labels as needed during the issue creation process.

Does GitHub issue triage work with referenced files to generate debugging hypotheses?

GitHub issue triage works with referenced files by optionally reading them to generate falsifiable prior hypotheses, integrating file validation into the bug tracking workflow for more actionable issue reports.

How do I integrate GitHub issue creation into a developer fix workflow?

Integrating GitHub issue creation into a developer fix workflow creates issues with prior hypotheses and links them to follow-up actions, such as running targeted fix commands on the selected issue number.

What limitations exist when using gh CLI for GitHub issue management and triage?

Limitations of using gh CLI for GitHub issue management include dependency on verified repository context and the need for existing or auto-created labels, which may constrain triage in complex multi-repository environments.