kaizen-file-issue

Creates a structured GitHub issue from a raw incident observation.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/Garsson-io/kaizen --skill kaizen-file-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kaizen-file-issue
Source: https://github.com/Garsson-io/kaizen/tree/main/.agents/skills/kaizen-file-issue
Command: npx skills add https://github.com/Garsson-io/kaizen --skill kaizen-file-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly convert a raw incident observation into a well-formed GitHub issue, focusing on the problem space rather than proposing a solution, and doing so in about two minutes.

Core Features & Use Cases

  • Automatically captures incidents described by observers and creates a structured issue ready for triage.
  • Enforces a consistent issue body format (Incident, Problem space, Directional guess) to speed review and assignment.
  • Supports routing to the correct repository and applies Kaizen workflow labels for visibility.

Quick Start

Describe the observed problem and trigger the kaizen-file-issue skill to file a GitHub issue in your issues repository.

Frequently Asked Questions about kaizen-file-issue

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

FAQPage Schema
How do I convert a raw incident observation into a structured GitHub issue?

To convert a raw incident observation into a structured GitHub issue, the skill automatically generates an issue body containing Incident, Problem space, and Directional guess sections for fast triage.

What is the best way to track kaizen incidents in a GitHub issues repository?

Tracking kaizen incidents involves routing structured observations to the appropriate host repository with standardized labels, ensuring the problem space is captured for review rather than proposing immediate solutions.

How do I file a GitHub issue fast without writing a full solution proposal?

You can file a GitHub issue in under two minutes by triggering the skill with a described problem, which formats the observation into a clean issue body focused strictly on the problem space.

Does the kaizen-file-issue workflow require specific GitHub labels for routing?

The workflow applies standardized Kaizen labels to route the generated issue to the correct repository, ensuring proper visibility and assignment during the triage process.

When should I use a structured GitHub issue format for incident tracking?

You should use a structured GitHub issue format for incident tracking when you observe a problem during kaizen-reflect, or when impediments require structured tracking to speed review and assignment.

Can I automate GitHub issue creation from text descriptions during incident response?

You can automate GitHub issue creation by providing a raw text description of an observed problem, which the skill processes into a well-formed issue ready for triage and assignment.