← Skills Library
Build & Deploy

Scaffold Tests

Zero to test suite in one command. Detects your stack, maps major modules, creates the directory structure, writes one real test file per module, and configures coverage. Gives you somewhere to start — not a finished suite.

How It Works

Scaffold Tests · Workflow
Detect stack, wire CI, write real starter tests, verify it runs.
▸TriggerBare repo, no tests · Zero-to-suite setup for any stack
1
Detect stack & framework
pytest · vitest · go test · cargo — never overwrites existing config
2
Install framework + CI workflow
Adds deps and a .github test workflow
3
Map modules & write test files
Routes · services · models — one file, real assertions, no expect(true)
4
Configure coverage floor
Sets the threshold and runs a baseline pass
5
Verify pipeline runsGATE
Run the suite end-to-end and report the coverage baseline
✕fail → Report gap list — you fill in the behavior
✓Working test scaffold · Structure + config + starter tests + a specific gap list
  1. Bare repo, no tests: Zero-to-suite setup for any stack
  2. Detect stack & framework: pytest · vitest · go test · cargo — never overwrites existing config
  3. Install framework + CI workflow: Adds deps and a .github test workflow
  4. Map modules & write test files: Routes · services · models — one file, real assertions, no expect(true)
  5. Configure coverage floor: Sets the threshold and runs a baseline pass
  6. Verify pipeline runs: Run the suite end-to-end and report the coverage baseline
  7. Working test scaffold: Structure + config + starter tests + a specific gap list
ↆ download card

Invocation Triggers

/scaffold-testsscaffold testsset up testingcreate test suiteadd tests

Use Cases

  • Bootstrap a test suite on a repo that has none
  • Get the right directory structure and config before writing feature code
  • See your coverage baseline and the specific gaps to fill next

The Problem

The pain is that starting from zero is harder than it should be. You know you need tests but not where to start. Two hours later you have a test that asserts `true === true` and a 0% passing rate on the things that matter.

What It Does

  1. 1
    Detect stack and existing test setup

    Checks for jest, vitest, pytest, go test, and cargo test. Does not overwrite existing config — safe to run on repos that have partial coverage.

  2. 2
    Map major modules

    Routes, services, utils, models, controllers — anything that is a real unit of behavior. Ignores generated files, node_modules, and dist artifacts.

  3. 3
    Create test directory structure

    Follows language conventions: `__tests__/` for JS/TS, `tests/` for Python, `*_test.go` for Go. Structure is set up before the first test file is written.

  4. 4
    Write one test file per module

    2–3 meaningful test stubs per file — real scenarios with real assertions, not `expect(true).toBe(true)`. You fill in the behavior; the scaffold gives you the shape.

  5. 5
    Configure coverage and report baseline

    Adds coverage config, runs a baseline pass, and reports what is covered, what is not, and what the floor should be. Gives you a specific gap list to act on.

What You Get / What It Doesn't Do

What you get
  • Test directory structure following language conventions
  • One test file per major module with 2–3 real assertion stubs
  • Working test config (jest/vitest/pytest/go/cargo)
  • Baseline coverage report
  • Specific list of the next gaps to fill
What it doesn't do
  • Write real tests — that is quality-team (Pro)
  • Guarantee a coverage floor — it gives you a floor to build from
  • Test UI components — focused on logic modules
  • Replace a QA strategy

Tips

Run before you write feature code, not after

The scaffold tells you how to test what you are about to build. Running it after means retrofitting — which is always harder.

The stubs are starting points, not finished tests

Write real behavior into them before calling this done. A stub with a TODO is a reminder, not a test.

If coverage is already over 30%, skip this

Use quality-check to see what you are missing. Scaffold-tests is for repos starting from zero.

Get the Skill

Free DownloadFREE

Scaffold Tests

The full SKILL.md — copy it into ~/.claude/skills/ and trigger it by name.

Commonly Used With

Build & DeployQuality CheckSingle-agent coverage scanner. Runs your test suite, ranks your top 5 riskiest untested paths by criticality, and gives you a prioritized fix list — no auto-fix, no parallel agents.Agent TeamsQuality TeamSpawn a 3-agent QA gate (Test Writer + Code Reviewer + Coverage Analyst) for pre-release quality assurance and coverage remediation.
Skills Library

29 more production skills ready to install.

Browse All Skills