A New Project Shouldn't Start With Zero Tests.
Point an agent at a fresh repo and the testsprite-onboard skill reads the codebase, creates a TestSprite project, authors roughly 8-15 starter tests, and runs the top 2-3 happy-path flows — one step instead of a blank slate.
Built Into the Same CLI You Already Run
testsprite-onboard turns "no tests yet" into a running starter suite in a single skill call.Reads Before It Writes
The testsprite-onboard skill looks at the codebase first — stack, routes, structure — before it creates a project or authors a single test.
Creates the Project For You
No manual setup wizard. The skill creates the TestSprite project as part of the same call, so there's nothing to configure by hand first.
Ships 8-15 Starter Tests
It authors roughly 8-15 starter tests sized to what it finds in the codebase — a real suite to start from, not one lonely smoke test.
Runs the Top Flows First
Instead of leaving every new test unverified, it runs the top 2-3 happy-path flows right away so you see real pass/fail results immediately.
$ testsprite setup --from-env --yes --agent claude Reading TESTSPRITE_API_KEY from environment... Installing testsprite-onboard skill for claude... Skill installed. > Set up TestSprite for this repo and seed a starter test suite, then smoke-run the most important flow. Reading codebase... Creating TestSprite project: "checkout-service" Authoring starter tests... 12 tests created Running top 3 happy-path flows... 3/3 passed
Stop Staring at an Empty Test Project
A fresh codebase and a blank test project usually means an hour of manual setup before anyone runs anything. The testsprite-onboard skill collapses that hour into one agent prompt — codebase in, a real starter suite running out.
Built for the First Five Minutes of a New Project
Works From One Prompt
No separate CLI dance — an agent prompt like "set up TestSprite for this repo and seed a starter test suite" is enough to trigger the skill.
Feeds the Rest of the CLI
Onboarding output is a real TestSprite project. Keep extending it with test create, test scaffold, or test create-batch as coverage grows.
Free Community Version
Offers a free community version, making it accessible to everyone.
Works Across Agent Tools
Install the onboarding skill for claude, cursor, cline, windsurf, antigravity, codex, copilot, or kiro with agent install.
Trusted By Businesses Worldwide
"TestSprite offers rich test case generation, clear structure, and easy-to-read code. It also supports simple online debugging with the ability to quickly expand by generating new test cases."
"TestSprite's automation helps us reduce tons of manual work. The developers can easily catch and resolve bugs earlier in the development process."
FAQ
What does the testsprite-onboard skill actually do?
It reads the codebase, creates a TestSprite project, authors roughly 8-15 starter tests, and runs the top 2-3 happy-path flows — all from a single agent prompt.
How many tests does it create?
Roughly 8-15 starter tests, sized to what the skill finds in the codebase — enough for a real starter suite, not just one smoke test.
Does it just create tests, or does it run them too?
Both. After authoring the starter tests, it runs the top 2-3 happy-path flows so you get real pass/fail results, not just a pile of unverified tests.
How do I trigger it?
With a plain-language prompt to your agent, for example: "Set up TestSprite for this repo and seed a starter test suite, then smoke-run the most important flow."
Do I need to install anything separately for my agent tool?
Run testsprite setup (or testsprite setup --from-env --yes --agent <name> for a non-interactive setup) with claude, cursor, cline, windsurf, antigravity, codex, copilot, or kiro as the agent — it installs the skill for that tool.