You build. We cover.

tailtest is a Claude Code plugin that automatically runs tests every time Claude writes or edits a source file -- no prompting required.

Full documentation at tailtest.com/docs

claude plugin marketplace add avansaber/tailtest
claude plugin install tailtest@avansaber-tailtest

Restart Claude Code after install. No other setup required.

claude plugin marketplace update avansaber-tailtest
claude plugin update tailtest@avansaber-tailtest

claude plugin remove tailtest@avansaber-tailtest

After any Claude-written file lands in your project:

1. tailtest generates scenarios that describe real business behavior -- not function signatures
2. It runs them using your existing test runner (pytest, vitest, jest, go test, and more)
3. Pass: tailtest: N scenarios -- all passed. Fail: one line surfaced, "want me to fix this?"

Python, TypeScript, JavaScript, Go, Ruby, PHP, Java, Kotlin, C#, Rust

Runners are auto-detected from pyproject.toml, package.json, go.mod, build.gradle.kts, *.csproj, *.sln, and other standard manifests.

Create .tailtest/config.json in your project root to control depth:

{ "depth": "standard" }

Options: simple (2-3 scenarios), standard (5-8, default), thorough (10-15).

See tailtest.com/docs/config for all options.

Same R1-R15 rule layer, same adversarial test mode, different host integration. This repo is the Claude Code variant.

• tailtest -- Claude Code plugin (hook-driven; this repo)
• tailtest-cursor -- Cursor plugin (hook-driven)
• tailtest-codex -- Codex CLI plugin (hook-driven)
• tailtest-cline -- Cline plugin (MCP-driven; reaches 8+ editors via Cline's host coverage)

See tailtest.com/demo/claude-code for a live walkthrough of this variant, or tailtest.com/comparison for a feature matrix across all four.

MIT