tobihagemann/comprehensive-test
skills/comprehensive-test/SKILL.md
Execute comprehensive, multi-level testing of the app covering basic functionality, complex operations, adversarial testing, and cross-cutting scenarios. Deeper than /smoke-test. Use when the user asks to "test thoroughly", "comprehensive test", "test all scenarios", "deep test", "test edge cases", "test everything", "break it", or "find bugs by testing".
$ install --global
skillsauthnpx skillsauth add tobihagemann/turbo comprehensive-testInstall 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 16, 2026, 1:24 AM6.2s1 file scanned
SKILL.md
- name:
- comprehensive-test
- description:
- Execute comprehensive, multi-level testing of the app covering basic functionality, complex operations, adversarial testing, and cross-cutting scenarios. Deeper than /smoke-test. Use when the user asks to \"test thoroughly\", \"comprehensive test\", \"test all scenarios\", \"deep test\", \"test edge cases\", \"test everything\", \"break it\", or \"find bugs by testing\".
Comprehensive Test
Execute comprehensive, multi-level testing that goes beyond smoke testing to actively find bugs through escalating test scenarios.
Step 1: Load or Create Test Plan
Check if .turbo/test-plan.md exists.
- If it exists — read the test plan and continue to Step 2. If the user specifies a narrower scope, filter the plan to relevant scenarios rather than executing all of them.
- If it does not exist — run the
/create-test-planskill first, then continue.
Step 2: Determine Testing Approach
Use the approach specified in the test plan. If the plan does not specify one, determine it using the same logic as /create-test-plan Step 3.
Step 3: Execute Tests by Level
Work through each level sequentially. Complete all tests in a level before moving to the next.
Execution Loop (Per Test)
- Set up the preconditions described in the test scenario
- Perform the exact steps
- Capture the result (screenshot, output, or state observation)
- Compare against the expected outcome
- Record PASS or FAIL with details
Level Progression
- Level 1: Basic Functionality — If any Level 1 test fails, report early and use
AskUserQuestionto ask whether to continue. Basic failures may indicate the feature is too broken for deeper testing. - Level 2: Complex Operations — Execute all tests regardless of individual failures.
- Level 3: Adversarial Testing — Execute all tests. Failures here are expected and valuable.
- Level 4: Cross-Cutting Scenarios — Execute all tests.
If a project-specific testing skill or MCP tool was identified in Step 2, use that. The paths below are fallbacks.
Web App Path
Start the dev server if not already running. Wait for it to be ready. If /agent-browser is available, run the /agent-browser skill. Otherwise, use claude-in-chrome MCP to interact with the app.
UI/Native App Path
Launch the app. Use computer-use MCP to interact with the UI.
CLI Path
Run commands directly.
Step 4: Report
Present results organized by level:
Comprehensive Test Results:
## Level 1: Basic Functionality (X/Y passed)
- [PASS] Test name: description
- [FAIL] Test name: description — [what went wrong]
## Level 2: Complex Operations (X/Y passed)
- [PASS] Test name: description
- [FAIL] Test name: description — [what went wrong]
## Level 3: Adversarial Testing (X/Y passed)
- [PASS] Test name: description
- [FAIL] Test name: description — [what went wrong]
## Level 4: Cross-Cutting Scenarios (X/Y passed)
- [PASS] Test name: description
- [FAIL] Test name: description — [what went wrong]
Overall: X/Y passed across all levels
For each failure, include the relevant screenshot, output, or state observation.
Update .turbo/test-plan.md by checking off completed tests and annotating results.
Rules
- Always clean up: close browser sessions, stop dev servers started by this skill.
- Never modify application code. This skill is read-only verification. Report failures without attempting to fix them.
- If the dev server fails to start, report the error and stop.
- Use the Monitor tool to tail app logs for errors or warnings while running tests, so backend failures surface alongside test observations.
- To diagnose failures, run the
/investigateskill on the test report.
Related Skills
tobihagemann/user-experience
development
VerifiedTrustedCommunity
Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and assessment.
377SKILL.mdUpdated Jun 18, 2026
tobihagemann/user-experience
development
VerifiedTrustedCommunity
Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and assessment.
377SKILL.mdUpdated Jun 18, 2026
tobihagemann/assess-technical-debt
development
VerifiedTrustedCommunity
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, and architecture rot. Ranks findings by impact and refactor effort into a report at .turbo/technical-debt.md. Use when the user asks to "assess technical debt", "find technical debt", "review technical debt", "what should we refactor", "find refactoring candidates", "where is the code rot", or "what's our worst code". Analysis-only — does not modify code.
377SKILL.mdUpdated Jun 15, 2026
tobihagemann/simplify-docs
development
VerifiedTrustedCommunity
Run a multi-agent review of code comments and markdown documentation for unnecessary content, then fix the issues. Covers what-restating comments, name-mirroring doc comments, status-update prose, and other documentation noise. Use when the user asks to "simplify docs", "simplify documentation", "clean up comments", "clean up docs", "review documentation", "strip unnecessary comments", "reduce doc noise", or "run simplify-docs".
377SKILL.mdUpdated May 15, 2026