cubetiq/debug
workflows/workflows/agent-environment-setup/platforms/claude/generated-skills/debug/SKILL.md
Investigate a failure systematically, confirm the root cause, and verify the fix path.
$ install --global
skillsauthnpx skillsauth add cubetiq/cubis-foundry 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 4, 2026, 9:59 AM11.4s1 file scanned
SKILL.md
- name:
- debug
- description:
- Investigate a failure systematically, confirm the root cause, and verify the fix path.
- license:
- MIT
- author:
- cubis-foundry
- route-kind:
- workflow
- route-id:
- debug
- platform:
- Claude Code
- command:
- /debug
- compatibility:
- Claude Code
Debug Workflow
What this workflow does
Turns a vague failure report into a reproducible symptom, a confirmed cause, and a verified fix path.
When to use
Use this when reproduction, diagnosis, and evidence matter more than immediately editing code.
Agent chain
debugger
Step details
- Reproduce or precisely restate the failure.
- Test hypotheses against evidence until the root cause is confirmed.
- Propose or apply the fix and verify that the symptom is gone.
Skill routing
- Always load
systematic-debugging. - Add the relevant domain skill only after the failure surface is known.
- Keep code-level unit and integration checks inside the owning language or framework skill.
- Use
web-testing,android-emulator-testing, orios-simulator-testingwhen the bug only proves out in a live browser or device runtime.
Context notes
Provide the observed symptom, expected behavior, reproduction steps, and recent changes if known.
Verification
The workflow is complete only when the root cause is explicit and the fix is validated against the original symptom.
Output contract
DEBUG_WORKFLOW_RESULT:
symptom: <failure>
root_cause: <cause>
evidence:
- <proof>
verification: <fix confirmation>
Follow-up items
Typical next step: /implement or /test
Related Skills
cubetiq/deep-research
tools
VerifiedTrustedCommunity
Use when investigating latest vendor behavior, comparing tools or platforms, verifying claims beyond the repo, or gathering external evidence before implementation.
1SKILL.mdUpdated Apr 4, 2026
cubetiq/database-design
documentation
VerifiedTrustedCommunity
Use when designing database schemas, normalization strategies, indexing plans, query optimization, and migration workflows for relational, document, or hybrid data stores.
1SKILL.mdUpdated Apr 4, 2026
cubetiq/csharp-best-practices
development
VerifiedTrustedCommunity
Use when writing, reviewing, or refactoring modern C#/.NET code, including minimal APIs, records, async streams, pattern matching, DI lifetimes, and memory-efficient performance tuning.
1SKILL.mdUpdated Apr 4, 2026
cubetiq/code-review
development
VerifiedTrustedCommunity
Use when conducting code reviews, building review checklists, calibrating review depth, providing structured feedback, or establishing team review practices. Covers review methodology, feedback patterns, automated checks, and batch review strategies.
1SKILL.mdUpdated Apr 4, 2026