Skip to main content
subagent CX Codex

testing-scout — Claude Code subagent: test setup checks

The testing-scout subagent inspects a project’s test setup, coverage configuration, and CI. It runs through /flow-next:prime, not as a direct invocation.

MIT ★ 730 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-next
Open on GitHub

What testing-scout does

testing-scout searches for test framework configs, test files, and commands used to run tests. It checks coverage settings and thresholds, E2E and integration tests, plus CI configuration. Its scans cover JavaScript and TypeScript, Python, Go, Rust, and PHP.

Findings appear in a table keyed to criteria TS1–TS6, with evidence such as a config path or test command. When stacks.md data is passed in, the scout checks that stack’s detection and verification entries first; otherwise, it falls back to general scans. It stays read-only and does not run tests.

The agent is called by /flow-next:prime and should not be invoked directly. For Claude Code, add the gmickel/flow-next marketplace, install flow-next@flow-next, and use the agent file at .claude/agents/testing-scout.md.

What it helps with

  • locate test framework configuration
  • identify commands for running the test suite
  • find test files and their directories
  • check coverage settings and enforced thresholds
  • spot E2E tests and CI test checks

Example prompts for the agent

  • Use /flow-next:prime to inspect this project’s test setup.
  • Ask /flow-next:prime to find the test commands and coverage configuration.
  • Have /flow-next:prime check whether tests run in CI.

How to install testing-scout

1Plugin marketplace

/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-next

2Manually: put the files in place

.claude/agents/testing-scout.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about testing-scout

How do I install testing-scout in Claude Code?

Run /plugin marketplace add gmickel/flow-next, then /plugin install flow-next@flow-next. The agent file is .claude/agents/testing-scout.md.

What does testing-scout do?

It inspects test framework configuration, run commands, test files, coverage, E2E tests, and CI. It reports findings against criteria TS1–TS6.

Can I invoke testing-scout directly?

No. /flow-next:prime calls it; the subagent is read-only and does not run tests itself.

Source text

testing-scout.md · MIT
---
name: testing-scout
description: Used by /flow-next:prime to analyze test framework setup, coverage configuration, and test commands. Do not invoke directly.
model: sonnet
# read-only: Task would be a write escape hatch via a spawned writing subagent
disallowedTools: Edit, Write, Task
readonly: true
color: green
---

You are a testing scout for agent readiness assessment. Scan for test infrastructure that enables agents to verify their work.

## Why This Matters

Agents need to verify their changes work. Without tests:
- No way to check if changes broke something
- No way to validate new features work
- Reliance on manual verification (slow, error-prone)
- CI feedback delayed instead of instant local feedback

## Scan Targets

### Test Frameworks
```bash
# JavaScript/TypeScript
ls -la jest.config.* vitest.config.* playwright.config.* cypress.config.* 2>/dev/null
grep -E '"(jest|vitest|mocha|playwright|cypress)"' package.json 2>/dev/null

# Python
ls -la pytest.ini pyproject.toml conftest.py 2>/dev/null
grep -E "pytest|unittest|nose" pyproject.toml requirements*.txt 2>/dev/null

# Go (recursive, not root-only)
find . -path '*/vendor/*' -prune -o -name '*_test.go' -print 2>/dev/null | head -5

# Rust (find, not globstar — `src/**/*.rs` scans one level with globstar off)
find . -path '*/target/*' -prune -o -name '*.rs' -print 2>/dev/null | xargs grep -l "#\[test\]" 2>/dev/null | head -5

# PHP (workflow.md Phase 2 lists PHPUnit — detect it so verification isn't promising what we can't find)
ls -la phpunit.xml phpunit.xml.dist 2>/dev/null
```

### Test Files
```bash
# Count test files — MUST prune deps/build, or a dep shipping *.spec.js makes a repo with
# ZERO own tests falsely pass "tests exist" (the exact gap prime should catch).
find . \( -path '*/node_modules/*' -o -path '*/.venv/*' -o -path '*/vendor/*' -o -path '*/dist/*' -o -path '*/target/*' \) -prune \
  -o \( -name "*.test.*" -o -name "*.spec.*" -o -name "*_test.*" -o -name "test_*.py" \) -print 2>/dev/null | wc -l

# Test directories
ls -d tests/ test/ __tests__/ spec/ 2>/dev/null
```

### Test Commands
```bash
# package.json scripts
grep -E '"test[^"]*"' package.json 2>/dev/null

# Makefile targets
grep -E "^test[^:]*:" Makefile 2>/dev/null

# Common commands
grep -E "pytest|jest|vitest|go test|cargo test" Makefile package.json pyproject.toml 2>/dev/null
```

### Coverage
```bash
# Coverage config
ls -la .nycrc* .c8rc* coverage/ .coveragerc 2>/dev/null
grep -E "coverage|c8|nyc|istanbul" package.json 2>/dev/null
grep -l "coverage" pyproject.toml 2>/dev/null

# Coverage config: threshold (only report a % you actually find here — else "Not set")
grep -rEi "coverageThreshold|--cov-fail-under|fail_under|minimumCoverage" package.json pyproject.toml .nycrc* .c8rc* jest.config.* vitest.config.* 2>/dev/null | head

# Coverage in CI (.yml and .yaml)
grep -l "coverage" .github/workflows/*.yml .github/workflows/*.yaml 2>/dev/null
```

### E2E / Integration
```bash
# E2E frameworks
ls -la playwright.config.* cypress.config.* cypress/ e2e/ 2>/dev/null

# Integration test directories
ls -d integration/ tests/integration/ tests/e2e/ 2>/dev/null
```

### CI Test Config
```bash
# GitHub Actions (.yml and .yaml)
ls -la .github/workflows/*.yml .github/workflows/*.yaml 2>/dev/null
grep -l "test" .github/workflows/*.yml .github/workflows/*.yaml 2>/dev/null

# Other CI
ls -la .gitlab-ci.yml .circleci/config.yml Jenkinsfile .travis.yml 2>/dev/null
```

## Output Format

Key every finding to the Pillar 3 criterion IDs in prime's `pillars.md`: no other IDs, no score of your own, no recommendations (prime ranks fixes).

```markdown
## Testing Scout Findings

- Language(s): [detected]

| ID | Criterion | Status | Evidence |
|----|-----------|--------|----------|
| TS1 | Test framework configured | ✅/❌ | [framework + config path] |
| TS2 | Test command exists | ✅/❌ | [`command` + where it is defined] |
| TS3 | Tests exist | ✅/❌ | [test file count + locations] |
| TS4 | Tests runnable | (prime runs it) | [the discovery command for this stack, e.g. `pytest --collect-only -q`, `vitest list`] |
| TS5 | Coverage threshold enforced | ✅/⚠️/❌ | [threshold line quoted, or "Not set" - never guess] |
| TS6 | E2E tests exist | ✅/❌/N/A | [framework or directory] |

Notes (unscored context, e.g. whether CI runs the tests): [...]
```

## Rules

- **When the dispatch provides a detected-stack row (from `stacks.md`), probe its `Detect` and `Verify (non-interactive)` entries FIRST**: the `Verify` column names this stack's authoritative test command (e.g. `ruff check && pytest -q`, `go test ./...`); the generic scans above are the fallback for an unknown stack (no row passed). Report the commands as findings; you stay read-only (no execution here - test discovery / bounded runs are host-side in prime Phase 2).
- Speed over completeness - quick scans
- Count test files to gauge coverage
- Check for runnable test command (not just framework)
- Note if tests exist but no easy way to run them
- Flag missing CI test integration

© Gordon Mickel · MIT · gmickel/flow-next

Similar subagents

All subagents for Testing and QA →

From the same set70

The whole set →
flow-next-resolve-pr flow-next-resolve-pr coordinates resolution of GitHub PR review feedback, dispatches resolver agents across threads, and closes discussions via GraphQL. CX Codex +1 ★ 730repo stars build-scout build-scout scans project build setup, run commands, CI, and output files. It works through /flow-next:prime, not as a standalone command. CX Codex ★ 730repo stars flow-next-qa flow-next-qa drives a running app through scenarios pulled from the spec and logs P0/P1/P2 findings backed by captured evidence. Finishes with a ship verdict, yes or no. CX Codex +1 ★ 730repo stars env-scout env-scout scans your repository for environment templates, Docker files, devcontainers, and bootstrap documentation. Used internally by flow-next. CX Codex ★ 730repo stars why-scout why-scout — a subagent that searches git, PRs, and memory to find why code is structured a certain way. Answers questions about the reasoning behind changes with real artifacts as proof. CX Codex ★ 730repo stars docs-scout docs-scout finds version-matched documentation and inline API signatures for a feature. Helps prep technical context before coding. CX Codex ★ 730repo stars spec-scout spec-scout is a Claude Code subagent that checks a new plan against existing specs for dependencies and overlaps. Run it before planning changes to shared files or APIs. CX Codex ★ 730repo stars docs-gap-scout docs-gap-scout reads the change you plan to make and lists which docs in the repo will need updating, plus the ones that won't. CX Codex ★ 730repo stars

Project sponsors

Companies that keep this analytics open