raisedadead/adhoc-debug
plugins/dp-cto/skills/adhoc-debug/SKILL.md
Use when you hit a bug, test failure, or unexpected behavior and want a structured investigation — 'debug this', 'why is this failing', 'find the root cause'.
$ install --global
skillsauthnpx skillsauth add raisedadead/dotplugins adhoc-debugInstall 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 26, 2026, 10:33 AM46.7s1 file scanned
SKILL.md
- name:
- adhoc-debug
- description:
- Use when you hit a bug, test failure, or unexpected behavior and want a structured investigation — 'debug this', 'why is this failing', 'find the root cause'.
- user-invocable:
- true
- context:
- fork
- agent:
- dp-cto:debugger
Ad-Hoc Debug
<!-- Two-layer deep-reasoning signal: debugger.md frontmatter `effort: high` sets agent-scope depth; this keyword sets skill-scope depth when the skill body is loaded without agent dispatch. Both are intentional. -->Use ultrathink for root-cause analysis — shallow reasoning finds the wrong cause.
Standalone debugging task. No tracker state, no task_id, no stage context. Works in any project.
Your Task
Investigate the error passed as arguments. If no error provided, ask the user: "What error or failing behavior should I investigate?" Include relevant file paths, stack traces, or reproduction steps if shared.
Protocol
Follow the 4-phase investigation:
- Reproduce — confirm the failure mode is observable. Run the failing command. Capture exact output.
- Analyze — read the relevant code with git history. Identify recent changes. Look for invariant violations.
- Hypothesize — form candidate root causes. Rank by evidence strength.
- Verify — prove the top hypothesis with a minimal test or repro. You MAY write a minimal repro script. You MUST NOT apply a fix.
Output Format
- Root cause — file:line with evidence quote
- Confidence — high / medium / low
- Suggested fix — what to change (describe, do not implement)
- Failed hypotheses — ruled-out candidates with why
No stage transition. No handoff. The user decides next steps.
Related Skills
raisedadead/self-develop
development
VerifiedTrustedCommunity
Use when the user shares a URL, names a resource from SOURCES.md, shares operational feedback, says 'adopt', 'learn from', 'what can we steal from', 'compare with', 'self-develop', or 'how do we get better'.
4SKILL.mdUpdated Apr 18, 2026
raisedadead/setup
tools
VerifiedTrustedCommunity
Use when you need to set up or rebuild the dp-lsp Docker image after installing the plugin — 'set up LSP', 'build the image', 'install language servers'.
4SKILL.mdUpdated Apr 18, 2026
raisedadead/tdd
development
VerifiedTrustedCommunity
Use when you want to write tests first, enforce test-driven development, or add test coverage — 'write tests for this', 'TDD this feature', 'add test coverage'. Strict RED-GREEN-REFACTOR discipline.
4SKILL.mdUpdated Apr 18, 2026
raisedadead/spec
testing
VerifiedTrustedCommunity
Use when starting major work that needs formal design review — cross-team changes, architectural decisions, or complex features where requirements need discovery before implementation.
4SKILL.mdUpdated Apr 18, 2026