/add-tests
Generate tests for a completed phase based on Evidence Review criteria and implementation
$ npx -y skills add backbay-labs/thrunt-god --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/add-tests
Context preview
What this command does when you run it.
Generate tests for a completed phase based on Evidence Review criteria and implementation
Command definition
add-tests.mdname: thrunt:add-tests description: Generate tests for a completed phase based on Evidence Review criteria and implementation argument-hint: "<phase> [additional instructions]" allowed-tools: - Read - Write - Edit - Bash - Glob - Grep - Task - AskUserQuestion argument-instructions: | Parse the argument as a phase number (integer, decimal, or letter-suffix), plus optional free-text instructions. Example: /thrunt:add-tests 12 Example: /thrunt:add-tests 12 focus on edge cases in the pricing module
<objective> Generate unit and E2E tests for a completed phase, using its SUMMARY.md, CONTEXT.md, and FINDINGS.md as specifications.
Analyzes implementation files, classifies them into TDD (unit), E2E (browser), or Skip categories, presents a test plan for user approval, then generates tests following RED-GREEN conventions.
Output: Test files committed with message `test(phase-{N}): add unit and E2E tests from add-tests command` </objective>
<execution_context> @~/.claude/thrunt-god/workflows/add-tests.md </execution_context>
<context> Phase: $ARGUMENTS
@.planning/STATE.md @.planning/HUNTMAP.md </context>
<process> Execute the add-tests workflow from @~/.claude/thrunt-god/workflows/add-tests.md end-to-end. Preserve all workflow gates (classification approval, test plan approval, RED-GREEN verification, gap reporting). </process>
Threat hunting command system for agentic IDEs
Repo: backbay-labs/thrunt-god
Other commands on thrunt-god.
- /help
Show available THRUNT threat hunting commands and artifact layout
Open command - /map-environment
Map available telemetry, query surfaces, tenants, retention windows, and investigation blind spots
Open command - /new-case
Initialize a threat hunting case from a signal, detection, intel lead, or analyst suspicion
Open command - /new-program
Initialize a threat hunting program with an environment map, tool inventory, huntmap, and empty execution directories
Open command - /plan
Create phase plans for a threat hunt with exact telemetry tasks, receipts, and query outputs
Open command - /publish
Publish a hunt as a case report, escalation, detection promotion, or leadership summary
Open command

