Write tests
with agent skills.

Choose a testing skill around the behavior you need to prove. A unit test, a browser journey and a final verification pass answer different questions, even when they all end with a green check.

Filter these skills by stack and access

Choose a skill

For new behavior, look for a test-driven workflow. For a user journey, look for browser or integration testing that matches your stack. For an existing change, use verification guidance that checks the requirement as well as the code.

Before you install

Provide the acceptance criteria, the repository test commands and any fixtures already available. Keep tests away from production data. Say whether the agent may add test dependencies or start services; neither follows automatically from writing a test.

Open a listing to read its source, access labels and review evidence before copying its install command. The automated scan covers SKILL.md, not referenced files or runtime behavior. Read the review limits.

Skills for this task

13 available skills, listed A to Z. Task labels help narrow the choice; they do not establish fit for your project.

Check the result

  1. 01

    Show that a new regression test fails for the intended reason before applying the fix.

  2. 02

    Cover a meaningful boundary or failure path as well as the happy path, using the public behavior where practical.

  3. 03

    Run the affected suite again after the final edit. Separate passed checks from skipped or blocked checks.