Partha Mehta

Two tasks: testsprite-onboard stands up a complete runnable TestSprite suite for a repo with no tests yet, deriving and batch-creating tests then smoke-running them green. testsprite-verify runs relevant tests against finished code changes and inspects failure artifacts before completion is reported.

Software engineers and QA-minded developers working in TestSprite-tested repositories. Onboard suits anyone starting a fresh project or running initial setup; verify suits developers finishing a feature or fix who must confirm changes pass existing or newly created tests before reporting done.

Use testsprite-onboard only when a repo has no TestSprite tests yet, right after initial setup, or when asked to bootstrap or seed tests. Use testsprite-verify whenever code outside docs or config changed and is about to be reported complete, running existing tests or creating new ones.

It creates a new TestSprite test matching the change type — either a frontend test plan or a backend Python assertion — then runs it to a terminal verdict. Any failure artifacts are inspected before the work is reported as done, ensuring uncovered changes still get verified.

For onboarding, the repo must have completed TestSprite setup with a target URL and authentication configured so a project can be created. For verification, the repo must already contain TestSprite tests, or the skill will author a new frontend plan or backend assertion to cover the change.