cs-issue

Routes bug reports through report, analysis, and fix stages with documented verification.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/wildlily1021/XW_Software --skill cs-issue-wildlily1021
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cs-issue
Source: https://github.com/wildlily1021/XW_Software/tree/main/.agents/skills/cs-issue
Command: npx skills add https://github.com/wildlily1021/XW_Software --skill cs-issue-wildlily1021

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bug fixes often happen ad hoc: no reproduction record, no root cause analysis, scope creep, and no verification trail. This Skill inserts a structured buffer between "found a problem" and "changed the code", so every fix leaves behind a report, an analysis, and a fix note that can be traced months later. ## Core Features & Use Cases - Workflow Routing: Inspects the current issue directory under codestable/issues/ and dispatches to the right sub-skill (cs-issue-report, cs-issue-analyze, or cs-issue-fix) based on which artifacts already exist. - Two Paths: A standard three-stage path (report → analyze → fix) with human checkpoints, plus a fast track for simple bugs where the root cause is obvious and the change touches only 1-2 spots. - Mandatory Fix Note: Every resolved issue produces a {slug}-fix-note.md with YAML frontmatter, enabling search by severity, tags, and status. - Use Case: A user says "there's a bug where the serial monitor crashes on empty data". The Skill checks for existing issue files, routes to the report stage, then guides analysis and a scoped fix with a verification record. ## Quick Start Tell the AI "I found a bug, help me fix it" and it will route you through the issue workflow starting with a problem report.

Frequently Asked Questions about cs-issue

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

FAQPage Schema
How do I document a bug fix so it can be traced later?▼

Record the issue in three Markdown artifacts: a report describing the problem, an analysis of the root cause, and a fix note covering what changed and how it was verified. Each file carries YAML frontmatter so it can be searched by severity, tags, and status.

What is a root cause analysis workflow for software bugs?▼

A root cause workflow separates problem reporting from analysis and fixing. First the symptoms and reproduction steps are recorded, then the code is examined to pinpoint the exact file and line causing the issue, and only then is a scoped fix applied and verified.

When should a bug fix skip full root cause analysis?▼

A fast track is appropriate only when the root cause is obvious at a specific file and line, the change touches one or two spots, and there is no cross-module risk. Bugs with multiple candidate causes or reproduction uncertainty should go through the full report and analysis stages.

How do I prevent scope creep when fixing bugs?▼

Keep the fix scoped to the analyzed root cause and record it in a dedicated fix note. If the fix reveals a need for new functionality, finish the issue documentation first and start a separate feature workflow rather than mixing changes.

What is the difference between a bug issue and a feature request workflow?▼

An issue covers something that already exists but behaves incorrectly, such as bugs, errors, or performance problems. A feature covers capability that never existed. The issue workflow routes bug reports only and redirects new-capability requests to the feature workflow.