cs-issue-fix

Name: cs-issue-fix
Availability: InStock
Author: liuzhengdong

Guide root-cause analysis, planned fixes, and verification within CodeStable.

1.1k|82|Updated Apr 12, 2026

Search Tags:#workflow #documentation #verification #code-review #root-cause-analysis #audit-trail #bug-fix

Ready to run

npx skills add https://github.com/liuzhengdongfortest/CodeStable --skill cs-issue-fix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cs-issue-fix
Source: https://github.com/liuzhengdongfortest/CodeStable/tree/main/cs-issue-fix
Command: npx skills add https://github.com/liuzhengdongfortest/CodeStable --skill cs-issue-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates structured bug-fix workflows by guiding users through root-cause analysis, planned fixes, and verification within CodeStable.

Core Features & Use Cases

Standard path and quick-entry flows drive repairs from declared analyses, ensuring changes stay scoped to the issue.
Generates a cs-issue-fix-fix-note.md documenting the complete fix lifecycle and attaches to the issue records for auditable traceability.
Provides a verification checklist to confirm reproduction steps, expected behavior, and regression safety.

Quick Start

Initiate the standard or quick-path fix flow and confirm scope before applying any changes.

Frequently Asked Questions about cs-issue-fix

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

FAQPage Schema

How do I automate structured bug fixes with root cause analysis and verification?▼

A structured bug fix workflow guides you through root-cause analysis, planned fixes, and verification. It enforces repairs to stay within declared scope and generates a fix-note document with verification results for audit trails.

What is the best way to document a bug fix lifecycle for audit traceability?▼

Documenting a bug fix lifecycle for audit traceability requires generating a fix-note markdown file. This file records the complete repair process, root-cause analysis, and verification results, attaching directly to issue records.

Can I use a quick-entry flow for rapid bug repairs without skipping verification?▼

Yes, quick-entry flows support rapid bug repairs while maintaining verification standards. Both standard and quick-entry paths require associated analysis documents and enforce verification checklists to confirm reproduction steps and regression safety.

Do I need an AGENTS.md file to guide code changes during issue resolution?▼

Yes, an AGENTS.md file is required to guide changes during issue resolution. The workflow mandates associated analysis documents and AGENTS.md to ensure all repairs remain strictly within the declared scope of the bug.

Why does my bug fix workflow require a verification checklist?▼

A verification checklist is required to confirm reproduction steps, expected behavior, and regression safety before completing a bug fix. This ensures the repair effectively resolves the issue without introducing new defects.