What problem does it solve?
Use this Skill when allcll-backend needs a bug fix that changes observable behavior such as validation, authorization, API responses, saved results, or notification states. It is intended for cases where you need to understand the current behavior, identify the expected behavior, and verify the impact before making changes.
Core Features & Use Cases
- Behavioral bug fixes: Correct logic that produces wrong responses, failed validations, broken permissions, or incorrect persistence outcomes.
- State and notification issues: Repair problems where data saves incorrectly, notification status is wrong, or a user-facing workflow does not match expectations.
- Impact-aware debugging: Suitable when you need to trace a reproducible issue, confirm the affected surface area, and validate the fix with evidence.
Quick Start
Diagnose the reported allcll-backend bug, explain the root cause, and propose the smallest safe code change with the verification steps I should run.