a11y-pass
FreeCatch the accessibility failures that ship in almost every AI-built UI. Use after building any interactive component.
The English summary is being prepared. Showing the original description.
Archive228/loopkit755Updated Jul 15, 2026
FreePublished on GitHub
systematic-debugging
Use for ANY bug, test failure, crash, or unexpected behavior. Forces reproduce-then-isolate before proposing a fix. Stops the agent from guessing.
The English summary is being prepared. Showing the original description.
See how to installFiles included (1)
- SKILL.md1.7 KB
SKILL.md (original)
Review the instructions the agent will receive before you install.
Systematic Debugging
The single most expensive agent failure: seeing an error and immediately generating a "fix" based on the error type, without reading what actually happened. Don't.
The loop
-
Read the whole error. The entire message and stack trace. A TypeError can mean a hundred different things — the trace tells you which one. Quote the exact line that throws.
-
Reproduce it first. If you can't reproduce it, you can't verify a fix. Write the smallest input that triggers it. "I think this fixes it" is gambling, not debugging.
-
Form one hypothesis, name it. "I think the value is null because the upstream call returns 204 with no body." State it before you touch anything.
-
Change one thing. Test. Repeat. If you change three things and it works, you don't know which one fixed it — and the other two may have added new bugs.
-
Fix the root cause, not the symptom. A null check that hides a null is not a fix. Find why it's null. The underlying bug will resurface differently if you only patch the crash.
Stop conditions
- If 3 hypotheses fail, STOP and report: what you tried, what you saw, what you suspect. "I've tried X and Y, here's the output, I think it's Z but I'm not sure" beats 20 silent random attempts.
- Never add a workaround you don't understand.
Output
End with: the root cause (one sentence), the minimal fix, and the test that now proves it.
Reviews
No reviews yet. Tell others what you thought.
Comments
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
More skills from this repository
Before compaction Loopkit extracts decisions into claude-decisions.json (machine-readable). Read it alongside claude-progress.txt at session start — prose is for humans, JSON is for the loop.
The English summary is being prepared. Showing the original description.
Archive228/loopkit755Updated Jul 15, 2026
Review a diff against the goal spec assuming the code is BROKEN. The reviewer that lives in the maker's head always agrees with itself — this pulls review into a hostile, separate pass. Invoke after every code change before marking work done.
The English summary is being prepared. Showing the original description.
Archive228/loopkit755Updated Jul 15, 2026
authz-check
FreeVerify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.
The English summary is being prepared. Showing the original description.
Archive228/loopkit755Updated Jul 15, 2026
Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.
The English summary is being prepared. Showing the original description.
Archive228/loopkit755Updated Jul 15, 2026
Before picking new work, smoke-test the last "completed" feature. If it's broken, revert and re-open it before touching anything else. Kills the "looks shipped, isn't shipped" bug across sessions.
The English summary is being prepared. Showing the original description.
Archive228/loopkit755Updated Jul 15, 2026