When an AI writes code and then reviews its own work, it can miss the same bugs twice. This skill helps you catch those hidden problems with automated regression tests. You can test API routes without a real database by using a sandbox mode. The tests run fast and find bugs that the AI overlooked.
This skill works best when you or your AI agent have changed backend logic or fixed a bug. It shows you how to set up tests with tools like Vitest and Next.js. The key idea is to write tests for bugs that were already found, not for code that works. This prevents the same bug from coming back.
One big pattern is the sandbox vs production path problem. The AI might fix the main code but forget to update the sandbox version. Automated tests catch this every time. Use /bug-check commands after changes to run these tests and keep your project safe.
Global
mkdir -p ~/.claude/skills/ai-regression-testingProject
mkdir -p .claude/skills/ai-regression-testingSource Repository
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