cs-issue

Route bug issues through a tri-stage workflow with YAML frontmatter and checkpoint governance.

1.1k|82|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/liuzhengdongfortest/CodeStable --skill cs-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cs-issue
Source: https://github.com/liuzhengdongfortest/CodeStable/tree/main/cs-issue
Command: npx skills add https://github.com/liuzhengdongfortest/CodeStable --skill cs-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bug issues often fail to capture clear reproduction steps, root causes, and verifiable fixes, causing repeated incidents and weak traceability. This skill enforces a structured tri-stage workflow to move from problem discovery through report, analysis, and fix notes, ensuring auditability and accountability.

Core Features & Use Cases

  • Structured routing: directs each bug into codestable/issues/{date}-{slug} with three required artifacts: {slug}-report.md, {slug}-analysis.md, and {slug}-fix-note.md.
  • Checkpoint governance: pauses at each stage for user validation before proceeding.
  • Fast-track option: when root cause is obvious, supports a rapid path to a single fix-note and closure.

Quick Start

Describe the bug and let cs-issue route it through report, analyze, and fix steps.

Frequently Asked Questions about cs-issue

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

FAQPage Schema
How do I structure bug tracking to capture reproduction steps and root causes?

To structure bug tracking, route issues through a tri-stage workflow that separates reports, analyses, and fixes into distinct Markdown artifacts, ensuring verifiable fixes and clear traceability across the issue lifecycle.

What is the best way to enforce standardized issue reporting in a development workflow?

The best way to enforce standardized issue reporting is by applying a guided workflow that mandates standardized YAML frontmatter and specific file naming conventions, preserving auditability and reproducibility for every bug.

How do I manage bug reports when the root cause is already obvious?

For bug reports with an obvious root cause, you can use a fast-track option to bypass the full analysis stage, enabling a rapid path to generating a single fix-note and closing the issue immediately.

Can I pause the bug resolution process for validation before completing a fix?

Yes, you can pause the bug resolution process using checkpoint governance, which halts the workflow at each stage to require user validation before proceeding to the next step.

Does tri-stage issue management work without external dependencies?

Yes, tri-stage issue management works without external dependencies, routing bugs directly into structured local Markdown files within the codestable/issues directory to capture reports, analyses, and fixes.