jamesaphoenix/test-diagnostics
.claude/skills/test-diagnostics/SKILL.md
Profile all test files to find slow, hanging, or failing tests. Use when tests seem slow or when vitest hangs.
$ install --global
skillsauthnpx skillsauth add jamesaphoenix/tx test-diagnosticsInstall 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 17, 2026, 2:14 AM27.9s2 files scanned
SKILL.md
- name:
- test-diagnostics
- description:
- Profile all test files to find slow, hanging, or failing tests. Use when tests seem slow or when vitest hangs.
- disable-model-invocation:
- true
- allowed-tools:
- Bash, Glob, Read
Test Diagnostics
Profile every test file in the monorepo individually to find slow, hanging, or failing tests.
Quick run
Run the diagnostics script:
.claude/skills/test-diagnostics/run-diagnostics.sh
Options:
--timeout 30— Kill tests after N seconds (default: 30)--slow-threshold 5— Report tests taking > N seconds as SLOW (default: 5)--dir ./test/integration— Only test files under a specific directory
After running
- Review the summary output
- For any HANG tests, read the test file and look for:
- Missing
afterAllcleanup or open connections - Servers or background processes that aren't shut down
- Infinite loops or unresolved promises
- File watchers that aren't cleaned up
- Missing
- For any FAIL tests, run them individually with verbose output:
bunx --bun vitest run <path> 2>&1 - For SLOW tests (>5s), check if they can be optimized:
- Are they spawning CLI subprocesses unnecessarily?
- Can expensive setup be shared across tests?
- Are there unnecessary sleeps or timeouts?
- Suggest concrete fixes for each issue found.
Related Skills
jamesaphoenix/verify-invariants
development
VerifiedTrustedCommunity
Implement and verify design doc invariants by annotating tests and source code with [INV-*] / @spec tags, then driving tx spec coverage from BUILD toward HARDEN (100% FCI). Works with any design doc that has an invariants block.
2SKILL.mdUpdated Apr 17, 2026
jamesaphoenix/task-spec-loop
data-ai
VerifiedTrustedCommunity
Link tasks to paired PRD/design specs, export all open work to markdown, and keep Ralph-style loops moving by creating tasks, subtasks, and dependency updates through tx primitives.
2SKILL.mdUpdated Apr 17, 2026
jamesaphoenix/skills-sync
development
VerifiedTrustedCommunity
Refresh bundled tx Claude Code and Codex skills in a project from the canonical tx source without manual copy and paste.
2SKILL.mdUpdated Apr 17, 2026
jamesaphoenix/ralph-loop
development
VerifiedTrustedCommunity
Run Ralph against either the full repo queue or tasks linked to one design doc, with injected task/spec/queue context for Codex or Claude runtimes.
2SKILL.mdUpdated Apr 17, 2026