Cs Issue

When you hit a bug, your instinct is to just fix it and move on, but that's how you end up debugging the same issue six months later with no context. This skill sits between "I found a problem" and "I'm changing code" to force a structured loop: report what's broken, analyze root cause, fix it with verification, and leave a paper trail in three markdown files under .codestable/issues/. It's a router that decides whether you need the full three-stage process or can take a fast path for obvious one-liners. The whole point is stopping you from scope creep fixes that touch five things when you only meant to fix one, and making sure future-you has reproduction steps and analysis when the bug comes back.

skills.sh installs: 1.2K
GitHub stars: 1.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add liuzhengdongfortest/codestable --skill cs-issue --agent claude-code

Installs into .claude/skills of the current project.

Files

cs-issue

把问题诊断清楚；获得修复授权时，再修根因并证明它修好了。

开工

有 .codestable/attention.md 就先读。
按错误信息与相关模块关键词检索 .codestable/lessons/、项目文档，以及存在的 v1 只读知识目录：.codestable/roadmap/、.codestable/features/、.codestable/issues/、.codestable/refactors/、.codestable/goals/、.codestable/compound/、.codestable/audits/、.codestable/brainstorms/、.codestable/feedback/；这个坑可能踩过，命中要报告来源路径。上述 v1 目录不得继续生成、原地改写或批量迁移，新结论按归属进入 v2 Epic、项目文档、ADR 或 lesson。
同一会话由 cs 交入且带已确认 handoff 时，直接消费目标入口、原始诉求、目标或期望行为、范围/非目标、验收、已核实仓库事实及来源、owner 已确认的术语与决策、未决风险、canonical 资产指针或资产候选；packet 精确范围内已确认的事项不重复询问。handoff 只证明当前会话共识，不扩大实现、commit、发布或写入授权，也不替代本 skill 的 review、验证与确认门槛；字段缺失、仓库事实冲突、出现会改变结果的新风险、缺少会改变方向的事实或超出已确认边界时再按本 skill 规则确认。
对照检查：目标（期望行为）、现场（复现条件与环境）、边界（哪些不能动）、验收（怎么算诊断清楚或修好）。缺少会改变诊断或修复方向的事实时先问用户，一次最多 3 个问题，形成共识即停。
诉求其实是新增能力而不是坏掉的行为时，转 cs-feat，不在 issue 里偷做。