hoangnguyen0403/common-debugging
agents/skills/common/common-debugging/SKILL.md
Troubleshoot systematically using the Scientific Method. Use when debugging crashes, tracing errors, diagnosing unexpected behavior, or investigating exceptions.
$ install --global
skillsauthnpx skillsauth add hoangnguyen0403/agent-skills-standard common-debuggingInstall 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: Apr 27, 2026, 11:52 PM188.0s1 file scanned
SKILL.md
- name:
- common-debugging
- description:
- Troubleshoot systematically using the Scientific Method. Use when debugging crashes, tracing errors, diagnosing unexpected behavior, or investigating exceptions.
Debugging Expert
Priority: P1 (OPERATIONAL)
Scientific Method
- OBSERVE: Gather data. What exactly happening?
- Logs, Stack Traces, Screenshots, Steps to Reproduce.
- HYPOTHESIZE: Formulate theory. "I think X causing Y because Z."
- EXPERIMENT: Test theory.
- Create reproduction case.
- Change one variable at time to validate hypothesis.
- FIX: Implement solution once root cause proven.
- VERIFY: Ensure fix works and doesn't introduce regressions.
Anti-Patterns
- No shotgun debugging: Prove root cause before changing code.
- No debug prints in production: Remove all print/console.log before commit.
- No symptom masking: Fix root cause; never swallow errors without handling.
Best Practices
- Diff Diagnosis: What changed since it last worked?
- Minimal Repro: Create smallest possible code snippet that reproduces issue.
- Rubber Ducking: Explain code line-by-line to inanimate object (or agent).
- Binary Search: Comment out half code to isolate failing section.
References
- Bug Report Template
Related Skills
hoangnguyen0403/common-operator-profile
testing
VerifiedTrustedCommunity
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
524SKILL.mdUpdated Jul 12, 2026
hoangnguyen0403/database-transactions
documentation
VerifiedTrustedCommunity
Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
524SKILL.mdUpdated Jun 19, 2026
hoangnguyen0403/database-schema-design
development
VerifiedTrustedCommunity
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
524SKILL.mdUpdated Jun 19, 2026
hoangnguyen0403/database-query-performance
data-ai
VerifiedTrustedCommunity
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.
524SKILL.mdUpdated Jun 19, 2026