Thomashighbaugh/debug
skills/debug/SKILL.md
Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction
$ install --global
skillsauthnpx skillsauth add Thomashighbaugh/opencode 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: Jun 21, 2026, 2:24 AM219.6s1 file scanned
SKILL.md
- name:
- debug
- description:
- Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction
- level:
- 2
Debug
Use this skill when the user wants help diagnosing a current OMC/OpenCode session problem, workflow breakage, or confusing runtime behavior.
Goal
Find the real failure signal quickly and explain the next corrective step.
Workflow
- Read the user's issue description carefully.
- Inspect the most relevant local evidence first:
- trace tools
- state tools
- notepad / project memory when relevant
- failing tests or commands
- Reproduce the issue narrowly if possible.
- Distinguish symptoms from root cause.
- Recommend the smallest next fix or verification step.
Rules
- Prefer real evidence over guesses.
- Use the trace/state surfaces when the issue involves orchestration, hooks, or agent flow.
- If the issue is actually a product/runtime bug rather than app code, say so plainly.
- Do not prescribe broad rewrites before isolating the failure.
Output
- Observed failure
- Root-cause hypothesis
- Evidence for that hypothesis
- Smallest next action
Related
traceskill — Evidence-driven causal investigation with competing tracer hypotheses
Related Skills
Thomashighbaugh/tool-creator
tools
VerifiedTrustedCommunity
Create valid, type-safe TypeScript tools for OpenCode — generates correct boilerplate, typed interfaces, and handler stubs. Use when building new tools for global config or per-project .opencode/tools/.
1SKILL.mdUpdated Jul 5, 2026
Thomashighbaugh/tree-of-thoughts
testing
VerifiedTrustedCommunity
Explore multiple solution branches in parallel, evaluate each, and recommend the best path. Use when the user explicitly invokes /ideation tree-of-thoughts or asks for "tree of thought" / "branching exploration".
1SKILL.mdUpdated Jul 1, 2026
Thomashighbaugh/self-consistency
testing
VerifiedTrustedCommunity
Run multiple independent reasoning passes and find consensus. Use when the decision is critically important, the stakes are high, or the user explicitly requests "run it multiple times" / "check consistency" / "self-consistency".
1SKILL.mdUpdated Jul 1, 2026
Thomashighbaugh/opro
testing
VerifiedTrustedCommunity
Optimization by PROmpting — generate candidate prompt variations, test each against a benchmark, and report the best performer. Use when the user invokes /ideation opro or asks for "prompt optimization" / "OPRO".
1SKILL.mdUpdated Jul 1, 2026