aiming-lab/debug-systematically
memory_data/skills/debug-systematically/SKILL.md
Use this skill when diagnosing a bug, unexpected behavior, test failure, or any situation where code does not behave as expected. Follow a structured debugging process instead of randomly changing code.
$ install --global
skillsauthnpx skillsauth add aiming-lab/metaclaw debug-systematicallyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 28, 2026, 2:49 PM36.7s1 file scanned
SKILL.md
- name:
- debug-systematically
- description:
- Use this skill when diagnosing a bug, unexpected behavior, test failure, or any situation where code does not behave as expected. Follow a structured debugging process instead of randomly changing code.
- category:
- coding
Debug Systematically
Process:
- Reproduce the bug with the smallest possible input.
- Isolate — narrow down which component/function causes it.
- Hypothesize — form a specific, falsifiable hypothesis.
- Test — verify or disprove the hypothesis with a minimal experiment.
- Fix — address the root cause, not just the symptom.
- Verify — re-run the failing test and related tests.
Useful tools: print/logging, pdb/ipdb, unit tests, git bisect.
Anti-patterns:
- Changing multiple things at once and not knowing what fixed it.
- Ignoring related test failures.
- Commenting out code instead of understanding it.
Related Skills
aiming-lab/visualization-selection
development
VerifiedTrustedCommunity
Use this skill when creating charts, plots, or dashboards. Choose the visualization type that best communicates the data relationship before writing any plotting code.
2,755SKILL.mdUpdated Mar 27, 2026
aiming-lab/verify-before-irreversible-action
testing
VerifiedTrustedCommunity
Use this skill before taking any action that is hard to reverse — deleting files, overwriting data, sending messages, pushing to remote, modifying production systems. Always pause, state what you are about to do, and confirm before executing.
2,755SKILL.mdUpdated Mar 27, 2026
aiming-lab/uncertainty-acknowledgment
research
VerifiedTrustedCommunity
Use this skill when you are not sure about a fact, have outdated knowledge, or the question is contested. Explicitly communicate the level of confidence instead of asserting uncertain things as fact.
2,755SKILL.mdUpdated Mar 27, 2026
aiming-lab/tool-selection-strategy
tools
VerifiedTrustedCommunity
Use this skill when deciding which tools to call in an agentic workflow. Always choose the minimal, most direct tool for each step and avoid redundant or speculative tool calls.
2,755SKILL.mdUpdated Mar 27, 2026