`bash
npm install --save-dev tdd-guard-vitest
`

Add to your vitest.config.ts:

`typescript
import { defineConfig } from 'vitest/config'
import { VitestReporter } from 'tdd-guard-vitest'

export default defineConfig({
test: {
reporters: [
'default',
new VitestReporter('/Users/username/projects/my-app'),
],
},
})
`

#### Jest

Install the tdd-guard-jest reporter in your project:

`bash
npm install --save-dev tdd-guard-jest
`

Add to your jest.config.ts:

`typescript
import type { Config } from 'jest'

const config: Config = {
reporters: [
'default',
[
'tdd-guard-jest',
{
projectRoot: '/Users/username/projects/my-app',
},
],
],
}

export default config
`

Note: For both Vitest and Jest, specify the project root path when your test config is not at the project root (e.g., in workspaces or monorepos). This ensures TDD Guard can find the test results. See the reporter configuration docs for more details:

- Vitest configuration
- Jest configuration

`bash
pip install tdd-guard-pytest
`

Configure the project root in your pyproject.toml:

`toml
[tool.pytest.ini_options]
tdd_guard_project_root = "/Users/username/projects/my-app"
`

Note: Specify the project root path when your tests run from a subdirectory or in a monorepo setup. This ensures TDD Guard can find the test results. See the pytest reporter configuration for alternative configuration methods (pytest.ini, setup.cfg).

`bash
composer require --dev tdd-guard/phpunit
`

For PHPUnit 9.x, add to your phpunit.xml:

`xml



/Users/username/projects/my-app



`

For PHPUnit 10.x/11.x/12.x, add to your phpunit.xml:

`xml





`

Note: Specify the project root path when your phpunit.xml is not at the project root (e.g., in subdirectories or monorepos). This ensures TDD Guard can find the test results. The reporter saves results to .claude/tdd-guard/data/test.json.

`bash
go install github.com/nizos/tdd-guard/reporters/go/cmd/tdd-guard-go@latest
`

Pipe go test -json output to the reporter:

`bash
go test -json ./... 2>&1 | tdd-guard-go -project-root /Users/username/projects/my-app
`

For Makefile integration:

`makefile
test:
go test -json ./... 2>&1 | tdd-guard-go -project-root /Users/username/projects/my-app
`

Note: The reporter acts as a filter that passes test output through unchanged while capturing results for TDD Guard. See the Go reporter configuration for more details.

`bash
cargo install tdd-guard-rust
`

Use it to capture test results from cargo test or cargo nextest:

`bash


With nextest (recommended)

`makefile
test:
cargo nextest run 2>&1 | tdd-guard-rust --project-root $(PWD) --passthrough
`

Note: The reporter acts as a filter that passes test output through unchanged while capturing results for TDD Guard. See the Rust reporter configuration for more details.

Type /hooks in Claude Code to open the hooks menu, then configure each hook. Use the same location for all hooks. See Settings File Locations for guidance.

PreToolUse Hook

1. Select PreToolUse - Before tool execution
2. Choose + Add new matcher... and enter: Write|Edit|MultiEdit|TodoWrite
3. Select + Add new hook... and enter: tdd-guard
4. Choose where to save

UserPromptSubmit Hook

1. Select UserPromptSubmit - When the user submits a prompt
2. Select + Add new hook... and enter: tdd-guard
3. Choose same location as PreToolUse

SessionStart Hook

1. Select SessionStart - When a new session is started
2. Select + Add new matcher... and enter: startup|resume|clear
3. Select + Add new hook... and enter: tdd-guard
4. Choose same location as previous hooks

`json
{
"hooks": {
"PreToolUse": [
{
"matcher": "Write|Edit|MultiEdit|TodoWrite",
"hooks": [
{
"type": "command",
"command": "tdd-guard"
}
]
}
],
"userpromptsubmit": [
{
"hooks": [
{
"type": "command",
"command": "tdd-guard"
}
]
}
],
"SessionStart": [
{
"matcher": "startup|resume|clear",
"hooks": [
{
"type": "command",
"command": "tdd-guard"
}
]
}
]
}
}
``