Testing and debugging
You want tests that prove the change, and a cause when it breaks.
Three skills to inspect.
Descriptions are brief. Open the repository for the full instructions.
- 01
/tddmattpocock/skillsTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests. - 02
/test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code - 03
/assessing-test-coveragebitwarden/ai-pluginsUse when determining what test coverage ALREADY exists for a specific change (a PR, Jira key, Tech Breakdown doc, Testmo CSV, changed paths, or named component). Triggers on "what's already tested", "does this PR have tests", "what coverage exists for", "is this component covered", or "which behaviors have no test today". This is a backward-looking inventory of existing coverage for a concrete change. Do NOT use it to recommend or decide which new tests to add ("should I add integration tests here", "are unit tests enough"), to design a test strategy or plan, to run or fix existing tests, or to explain testing concepts like the test pyramid or which layers a repo uses โ those are all out of scope.
Browse the rest.
These all target the same kind of work.
Showing 18 of 79