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.
npx skills add https://github.com/liuzhengdongfortest/codestable --skill cs-issue