Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Provides a 7-step debugging protocol plus language-specific commands to systematically identify, verify, and fix software bugs across multiple environments.
Provides a 7-step debugging protocol plus language-specific commands to systematically identify, verify, and fix software bugs across multiple environments.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Systematic debugging methodology and language-specific debugging commands.
Reproduce โ Get it to fail consistently. Document exact steps, inputs, and environment. Isolate โ Narrow scope. Comment out code, use binary search, check recent commits with git bisect. Hypothesize โ Form a specific, testable theory about the root cause. Instrument โ Add targeted logging, breakpoints, or assertions. Verify โ Confirm root cause. If hypothesis was wrong, return to step 3. Fix โ Apply the minimal correct fix. Resist the urge to refactor while debugging. Regression Test โ Write a test that catches this bug. Verify it passes.
# Node.js debugger node --inspect-brk app.js # Chrome DevTools: chrome://inspect # Console debugging console.log(JSON.stringify(obj, null, 2)) console.trace('Call stack here') console.time('perf'); /* code */ console.timeEnd('perf') # Memory leaks node --expose-gc --max-old-space-size=4096 app.js
# Built-in debugger python -m pdb script.py # Breakpoint in code breakpoint() # Python 3.7+ # Verbose tracing python -X tracemalloc script.py # Profile python -m cProfile -s cumulative script.py
# LLDB debugging lldb ./MyApp (lldb) breakpoint set --name main (lldb) run (lldb) po myVariable # Xcode: Product โ Profile (Instruments)
/* Outline all elements */ * { outline: 1px solid red !important; } /* Debug specific element */ .debug { background: rgba(255,0,0,0.1) !important; }
# HTTP debugging curl -v https://api.example.com/endpoint curl -w "@curl-format.txt" -o /dev/null -s https://example.com # DNS dig example.com nslookup example.com # Ports lsof -i :3000 netstat -tlnp
git bisect start git bisect bad # Current commit is broken git bisect good abc1234 # Known good commit # Git checks out middle commit โ test it, then: git bisect good # or git bisect bad # Repeat until root cause commit is found git bisect reset
ErrorLikely CauseFixCannot read property of undefinedMissing null check or wrong data shapeAdd optional chaining (?.) or validate dataENOENTFile/directory doesn't existCheck path, create directory, use existsSyncCORS errorBackend missing CORS headersAdd CORS middleware with correct originsModule not foundMissing dependency or wrong import pathnpm install, check tsconfig pathsHydration mismatch (React)Server/client render different HTMLEnsure consistent rendering, use useEffect for client-onlySegmentation faultMemory corruption, null pointerCheck array bounds, pointer validityConnection refusedService not running on expected portCheck if service is up, verify port/hostPermission deniedFile/network permission issueCheck chmod, firewall, sudo
# What's using this port? lsof -i :PORT # What's this process doing? ps aux | grep PROCESS # Watch file changes fswatch -r ./src # Disk space df -h # System resource usage top -l 1 | head -10
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.