Install
$ agentstack add skill-cruxexperts-localsetup-ls-debug-pro ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ● Network access Used
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Debug Pro
Systematic debugging methodology and language-specific debugging commands for application code, CSS/layout, network issues, and git bisect workflows.
Source note: imported from debug-pro by cmanfre7; provenance was previously recorded in release-only _meta.json metadata with upstream version 1.0.0.
The 7-Step Debugging Protocol
- 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.
Language-Specific Debugging
JavaScript / TypeScript
# 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
Python
# 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
Swift
# LLDB debugging
lldb ./MyApp
(lldb) breakpoint set --name main
(lldb) run
(lldb) po myVariable
# Xcode: Product -> Profile (Instruments)
CSS / Layout
/* Outline all elements */
* { outline: 1px solid red !important; }
/* Debug specific element */
.debug { background: rgba(255,0,0,0.1) !important; }
Network
# HTTP debugging
curl -v https://api.example.com/endpoint
curl --silent --show-error --output /dev/null \
--write-out 'status=%{http_code} dns=%{time_namelookup}s connect=%{time_connect}s tls=%{time_appconnect}s first_byte=%{time_starttransfer}s total=%{time_total}s\n' \
https://example.com
# DNS
dig example.com
nslookup example.com
# Ports
lsof -i :3000
netstat -tlnp
Git Bisect
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
Common Error Patterns
| Error | Likely Cause | Fix | |-------|-------------|-----| | Cannot read property of undefined | Missing null check or wrong data shape | Add optional chaining (?.) or validate data | | ENOENT | File/directory doesn't exist | Check path, create directory, use existsSync | | CORS error | Backend missing CORS headers | Add CORS middleware with correct origins | | Module not found | Missing dependency or wrong import path | npm install, check tsconfig paths | | Hydration mismatch (React) | Server/client render different HTML | Ensure consistent rendering, use useEffect for client-only | | Segmentation fault | Memory corruption, null pointer | Check array bounds, pointer validity | | Connection refused | Service not running on expected port | Check if service is up, verify port/host | | Permission denied | File/network permission issue | Check chmod, firewall, sudo |
Quick Diagnostic Commands
# 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
2026-07 Refresh Note
Compared against upstream debugging workflow sources during the skill import wave. Keep the LocalSetup seven-step protocol as the stronger default: reproduce, isolate, hypothesize, instrument, verify, fix, and add a regression test.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: CruxExperts
- Source: CruxExperts/localsetup
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.