What problem does it solve?
When a user's report indicates actual behavior diverges from expected behavior, this Skill enforces a structured remediation and learning process so fixes don't remain one-off patches. It prevents silent bug fixes by ensuring root cause analysis, evaluation of whether knowledge should be persisted, and a clear summary is always produced.
Core Features & Use Cases
- Automatic trigger and classification: Detects bug reports in developer conversations and GitHub issues and distinguishes bugs from feature requests, questions, or docs.
- Five-step enforced workflow: Repair the issue, perform root cause analysis, evaluate whether the learning belongs in cookbook/memory/workflow, perform the write or recommend alternatives, and output a mandatory assessment summary.
- Actionable guidance: Recommends whether to add type annotations, lint rules, tests, or a cookbook entry, and lists exact files changed when writing is performed.
- Use case: Triage a failing QA report or GitHub issue, patch the regression, decide if the cause is an external library pitfall or a hidden timing bug, and record the decision into project documentation or automated checks.
Quick Start
Triage this report as a bug, fix the failure, analyze the root cause, evaluate whether to write a cookbook or update tests/linting, and produce a final summary of actions and file changes.
