Aisles / Testing and debugging
Write tests for what changed, fix failures without weakening tests, and debug with evidence.
Debug a bug with hypotheses instead of guesses. Reproduce it, isolate it, verify the root cause, make the smallest fix and add a regression test. Use when the user reports a bug, an error, a crash or unexpected behavior and the cause is unknown. Do not use for planned features or refactors.
View skill★ 2
Fix failing tests from trimmed runner output, find the real cause, and never weaken an assertion without asking. Use when tests fail, CI is red, or the user asks to fix failing tests. Do not use to write new tests or to make a red suite green by deleting or skipping tests.
View skill★ 2
Write tests only for the code that changed, using the project's own test framework and conventions, then run them. Use when the user asks to add tests, or after changing logic that has no tests. Do not use to rewrite a whole test suite or to chase coverage numbers.
View skill★ 2
Skills by other authors. We link to them and show their license. We do not host them and our CLI does not install them.
A disciplined process for bugs, test failures and unexpected behavior.
Open on GitHub
Write the test first when implementing a feature or fixing a bug.
Open on GitHub
Test and debug local web apps with Playwright, including screenshots and browser logs.
Open on GitHub