testsprite-verify

Runs TestSprite CLI tests against shipped code changes and reports terminal verdicts.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/TEC037/FitAi --skill testsprite-verify-tec037
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testsprite-verify
Source: https://github.com/TEC037/FitAi/tree/main/.claude/skills/testsprite-verify
Command: npx skills add https://github.com/TEC037/FitAi --skill testsprite-verify-tec037

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After finishing a feature or fix, developers often report work as done based only on unit tests or code review, missing bugs that only appear for real users. This Skill enforces a verification loop that actually runs TestSprite tests against the change before declaring completion. ## Core Features & Use Cases - Mandatory verification loop: Requires at least one TestSprite run to a terminal verdict (passed/failed/blocked/inconclusive) before any feature is reported done. - Flexible test sourcing: Runs an existing test that covers the change, creates a new frontend plan or backend Python assertion test, or batches multiple frontend plans for coverage sets. - Failure triage: Distinguishes plan-quality problems from real product bugs, downloads failure artifacts, and reports root-cause hypotheses without auto-fixing. - Use Case: You just modified a checkout component in a TestSprite-wired repo. The Skill finds or drafts a matching frontend plan, runs it via testsprite test run --wait against the deployed preview URL, inspects the result, and reports the verdict with a dashboard link. ## Quick Start Verify my just-finished feature by running the relevant TestSprite test against the deployed preview URL and tell me the verdict.

Frequently Asked Questions about testsprite-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a code change with TestSprite before marking it done?

Run at least one TestSprite test to a terminal verdict using testsprite test run <id> --wait for an existing test, or testsprite test create --run --wait for a new one. Unit tests, typechecks, and lint do not count as verification.

How do I test a change that is only running locally with TestSprite?

Use testsprite test run <test-id> --local <port> instead of --target-url, which tunnels your loopback address to the test runner. This works for frontend tests only and requires an API key with the run:tunnel scope.

When can I skip running a TestSprite test after a change?

Skip only for docs-only edits, pure build or config changes like tsconfig or lockfile bumps, or when the repo is not wired to TestSprite at all. Every other code change requires at least one test run to a terminal verdict.

Why did my TestSprite backend test pass without running its assertions?

The runner executes the file top-to-bottom and does not auto-discover test functions like pytest. You must explicitly call your test_* functions at the end of the file, or defined-but-uncalled tests silently pass.

What does TestSprite exit code 7 mean on a test run?

Exit code 7 means the run timed out and should be treated as inconclusive, not a regression. Resume it with testsprite test wait <run-id>, except for --local runs where the tunnel closed and you must re-run instead.