lobster-debugging
by 王晓菲
A systematic 4-phase debugging framework to find root causes, eliminate flaky tests, and prevent regressions.
- Eliminate flaky test suites by replacing timeouts with event-driven logic
- Perform deep root-cause analysis on complex, multi-component system failures
- Implement defense-in-depth guards to prevent recurring bug categories
Free
One-time purchase · Own forever
See it in action
[ROOT CAUSE FOUND]: Race condition in Auth Provider. [PREVENTION]: Replaced 500ms sleep with Promise.all() synchronization. [UNIT TEST]: test_auth_persistence_on_slow_network verified. [REGRESSION]: Validated against 4 existing auth edge cases. Result: Bug eliminated, not patched.
lobster-debugging
by 王晓菲
A systematic 4-phase debugging framework to find root causes, eliminate flaky tests, and prevent regressions.
Free
One-time purchase · Own forever
Included in download
- Downloadable skill package
- Instant install
See it in action
[ROOT CAUSE FOUND]: Race condition in Auth Provider. [PREVENTION]: Replaced 500ms sleep with Promise.all() synchronization. [UNIT TEST]: test_auth_persistence_on_slow_network verified. [REGRESSION]: Validated against 4 existing auth edge cases. Result: Bug eliminated, not patched.
About This Skill
What it does
Lobster Debugging is a rigorous, 4-phase framework designed to eliminate the "guess-and-check" cycle that plagues modern software development. It transforms your AI agent from a simple code-patcher into a systematic forensic investigator. Instead of applying shallow fixes, it enforces a strict protocol: investigation, condition-based synchronization, defense-in-depth, and academic verification.
Why use this skill
Standard LLMs often rush to provide the first plausible-looking fix, which leads to regression and technical debt. This skill implements the 'Iron Law' of debugging: no fixes allowed without proven root cause isolation. It prevents common pitfalls like "magic" sleep timers, flaky test patches, and symptom-only repairs. By using this skill, you ensure that every bug fixed is a bug that never returns.
How it works
- Phase 1: Investigation: Systematic binary search of the codebase and diagnostic instrumentation.
- Phase 2: Synchronization: Replacing flaky timeouts with robust event-based waiting.
- Phase 3: Defense-in-Depth: Implementing guards that prevent entire classes of similar vulnerabilities.
- Phase 4: Verification: Proving the fix handles edge cases and handles regression testing.
Use Cases
- Eliminate flaky test suites by replacing timeouts with event-driven logic
- Perform deep root-cause analysis on complex, multi-component system failures
- Implement defense-in-depth guards to prevent recurring bug categories
- Automate regression test generation for every bug fix discovered
How to Install
unzip lobster-debugging.zip -d ~/.claude/skills/Reviews
No reviews yet — be the first to share your experience.
Only users who have downloaded or purchased this skill can leave a review.
No reviews yet — be the first to share your experience.
Only users who have downloaded or purchased this skill can leave a review.
Security Scanned
Passed automated security review
Permissions
No special permissions declared or detected
Tags
Creator
Frequently Asked Questions
Learn More About AI Agent Skills
Similar Skills
code-reviewer
Reviews your code for bugs, security vulnerabilities, logic errors, performance issues, and style violations. Organizes findings by severity and suggests fixes with code examples.
env-doctor
Diagnoses why your project will not start. Checks runtime versions, dependencies, environment variables, databases, ports, and build artifacts systematically.
diagnosing-rag-failure-modes
RAG fails quietly. It retrieves documents, returns confident-looking answers, and misses the question entirely — because the question required connecting facts across documents, reasoning about sequence, or tracing causation. This skill gives you a five-question diagnostic checklist that classifies any failing query as either RAG-safe or structurally RAG-incompatible, then maps it to the specific failure pattern and the architectural fix that resolves it.
git-commit-writer
Writes conventional commit messages by analyzing your staged git changes. Detects commit type, scope, and breaking changes automatically.