Write Tests
neolabhq/context-engineering-kitAutomatically adding tests for your local code changes helps catch bugs early. The skill checks what files you have changed and creates tests for the critical business logic in those changes. It works with both uncommitted work and the latest commit.
You do not need to write every test by hand. For simple single‑file edits the skill writes tests directly. For multiple files or complex logic it uses specialized agents to analyze and create thorough test coverage. This saves you time and ensures no important code path is missed.
The skill preserves your existing tests and follows your project’s testing style. It first runs the full test suite to set a baseline, then carefully adds only the new tests needed. The result is safer code and faster development.
Add Write Tests skill to your workflow
Global
mkdir -p ~/.claude/skills/write-testsProject
mkdir -p .claude/skills/write-testsSource Repository
More Testing & QA Claude Code Skills
Grill Memattpocock/skills
Stress-test your plan with relentless questions until we both understand
Tddmattpocock/skills
Write one test at a time then code to make it pass
Test Driven Developmentobra/superpowers
Write a failing test first then code just enough to pass
Qamattpocock/skills
Turn bug reports into GitHub issues through natural conversation without technical fuss
Migrate To Shoehornmattpocock/skills
Replace unsafe as assertions with type-safe partial test data easily
Webapp Testinganthropics/skills
Test your local web apps quickly with Playwright automation and screenshots
Playwright Best Practicescurrents-dev/playwright-best-practices-skill
Master Playwright testing with best practices for reliable and fast tests
Google Agents Cli Evalgoogle/agents-cli
Run evaluations on your AI agent, find failures, and improve its quality step by step