yun520-1/mark-heartflow-skill/skills/debug-pro/SKILL.md
debug-pro
Systematic debugging methodology and language-specific debugging commands.
- Source repository stars
- 36
- Declared platforms
- 0
- Static risk flags
- 3
- Last source update
- 2026-07-28
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
Systematic debugging methodology and language-specific debugging commands.
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/yun520-1/mark-heartflow-skill --skill "skills/debug-pro"Inspect the Agent Skill "debug-pro" from https://github.com/yun520-1/mark-heartflow-skill/blob/20bbbb4eacf56c941ddc3420dcbc81c04d55ec5c/skills/debug-pro/SKILL.md at commit 20bbbb4eacf56c941ddc3420dcbc81c04d55ec5c. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
The 7-Step Debugging Protocol
1. Reproduce — Get it to fail consistently. Document exact steps, inputs, and environment. 2. Isolate — Narrow scope. Comment out code, use binary search, check recent commits with git bisect. 3. Hypothesize — Form a specific, testable theory about the root cause. 4. Instrument…
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. - 02
What's this process doing?
Review the “What's this process doing?” section in the pinned source before continuing.
Review and apply the “What's this process doing?” source section. - 03
System resource usage
Review the “System resource usage” section in the pinned source before continuing.
Review and apply the “System resource usage” source section. - 04
Language-Specific Debugging
Review the “Language-Specific Debugging” section in the pinned source before continuing.
Review and apply the “Language-Specific Debugging” source section.
Permission review
Static risk signals and limitations
Runs scripts
The documentation asks the agent to run terminal commands or scripts.
# Node.js debuggerRuns scripts
The documentation asks the agent to run terminal commands or scripts.
node --inspect-brk app.jsNetwork access
The documentation includes network, browsing, or remote request actions.
curl -v https://api.example.com/endpointNetwork access
The documentation includes network, browsing, or remote request actions.
curl -w "@curl-format.txt" -o /dev/null -s https://example.comWrites files
The documentation asks the agent to create, modify, or delete local files.
| `ENOENT` | File/directory doesn't exist | Check path, create directory, use `existsSync` |Evidence record
Why each signal appears
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 57/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 36 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- yun520-1/mark-heartflow-skill
- Skill path
- skills/debug-pro/SKILL.md
- Commit
- 20bbbb4eacf56c941ddc3420dcbc81c04d55ec5c
- License
- Not declared
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
debug-pro
Systematic debugging methodology and language-specific debugging commands.
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 -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
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
Alternatives
Compare before choosing
K-Dense-AI/scientific-agent-skills
simpy
Build, inspect, test, and analyze bounded process-based discrete-event simulations with SimPy, including events, resources, interrupts, monitoring, replications, warm-up, and reproducible output analysis.
affaan-m/ECC
python-testing
Python testing best practices using pytest including fixtures, parametrization, mocking, coverage analysis, async testing, and test organization. Use when writing or improving Python tests.
github/awesome-copilot
flowstudio-power-automate-build
Build, scaffold, and deploy Power Automate cloud flows using the FlowStudio MCP server. Your agent constructs flow definitions, wires connections, deploys, and tests — all via MCP without opening the portal. Load this skill when asked to: create a flow, build a new flow, deploy a flow definition, scaffold a Power Automate workflow, construct a flow JSON, update an existing flow's actions, patch a flow definition, add actions to a flow, wire up connections, or generate a workflow definition from
Jeffallan/claude-skills
legacy-modernizer
Designs incremental migration strategies, identifies service boundaries, produces dependency maps and migration roadmaps, and generates API facade designs for aging codebases. Use when modernizing legacy systems, implementing strangler fig pattern or branch by abstraction, decomposing monoliths, upgrading frameworks or languages, or reducing technical debt without disrupting business operations.