test-driven-development
Requires writing a test before implementation and observing its failure. Then guides writing minimal code to pass, ensuring the test checks behavior.
Your agent can do more. Find the skill that makes it happen.
Find your next superpower If you are an agent, refer to our llms.txt for full access.Requires writing a test before implementation and observing its failure. Then guides writing minimal code to pass, ensuring the test checks behavior.
Guides test-driven development for new features and bug fixes. Applies before implementation code is written.
Uses a failing behavioral test to guide implementation of a feature or bug fix. Follows with refactoring and relevant regression checks.
Runs tests and systematically fixes failing tests using smart error grouping. Applies when test suites fail or users request fixes to make tests pass.
Find caller-visible production changes existing tests would miss through pseudo-mutation analysis; verify candidates or close gaps only when requested. Includes read-only per-test composition for grading. Polyglot. USE FOR: would tests catch a bug, behavioral blind spots, surviving mutations. DO NOT USE FOR: concrete fix/feature revision proof (test-value-evidence); suite taxonomy (test-tagging); .NET coverage, Cobertura, plateaus or coverage-backed priorities (coverage-anal…
Applies universal testing rules to generated or modified test code before presentation, commit, or merge. Covers common Python, PHP, JavaScript, TypeScript, and Go test formats and can guide test writing when explicitly invoked.
Selects unit, deterministic, or evaluation tests for a Claude Code harness and writes a passing test. Checks hooks, skill triggers, injected context, tool-contract compliance, files, and side effects, including intercepting calls without executing them.
Creates unit, integration, and end-to-end tests, mocking strategies, test architectures, and defect reports. Covers coverage gaps, flaky tests, regression automation, k6 or Artillery performance tests, and OWASP security testing.
Reviews test quality using supplied tests and results. Evaluates assertions, negative cases, and regression coverage without executing tests or guaranteeing coverage.
Create task scenarios for an existing usability study. Include realistic tasks, success criteria, and notes for the facilitator.
Creates test scenarios with objectives, starting conditions, user roles, step-by-step actions, and expected results. Supports QA test cases, test plans, acceptance testing, and feature validation.
Produces formal, severity-ranked assessments using research-backed test smell categories across languages. Covers smells such as Assertion Roulette, Mystery Guest, Eager Test, Sleepy Test, and Conditional Test Logic.
Skills give your agent reusable instructions for a specific job. Pick one, read what it does, and bring it into your workflow.
A name only tells half the story. Search the full description and instructions to find the right fit.
Read the skill, visit its source, and see exactly what you’re adding to your agent.
Copy the install command from a skill page and run it in your project.
npx skillycli add owner/repo --skill name