Testing skills
Ordered by popularity: GitHub stars and install counts from the source. Only cards with a checked description are included.
-
1. skill-creator
Creates and refines skills, then tests them with prompts, evaluations, and performance checks.
skill · ★ 183,434 · ↓ 414,180 · Apache-2.0
-
2. improve-codebase-architecture
This skill scans a codebase for architectural friction, then builds a visual HTML report with refactoring candidates. Use it before a deeper architecture review.
skill · ★ 302,251 · ↓ 1,163,035 · MIT
-
3. tdd
Guides the red-green TDD loop: ensures tests are written first, keep them at public interfaces, and avoid coupling to implementation details.
skill · ★ 302,251 · ↓ 1,141,062 · MIT
-
4. prototype
Creates throwaway prototypes for checking state logic or exploring UI before committing the decision to the main codebase.
skill · ★ 302,251 · ↓ 986,201 · MIT
-
5. codebase-design
This skill helps design modules with small interfaces and hidden complexity. Use it when refactoring code, choosing a seam, or making tests easier to write.
skill · ★ 302,251 · ↓ 850,344 · MIT
-
6. diagnosing-bugs
This skill guides an agent through reproducible diagnosis of hard bugs and performance regressions. Use it when code fails, produces wrong results, or becomes slow.
skill · ★ 302,251 · ↓ 834,802 · MIT
-
7. implement
Implements work from a specification or tickets, following a test-driven flow and ending with review and a commit. Use it when a coding task needs a defined delivery routine.
skill · ★ 302,251 · ↓ 774,700 · MIT
-
8. to-spec
Turns the current conversation and repository context into a spec, then publishes it to the project issue tracker. Use it when a feature discussion is ready to hand off to an agent.
skill · ★ 302,251 · ↓ 715,388 · MIT
-
9. webapp-testing
This skill tests local web apps with Playwright, helping agents debug UI behavior, capture screenshots, and inspect browser logs.
skill · ★ 183,434 · ↓ 186,758 · Apache-2.0
-
10. setup-pre-commit
This skill configures pre-commit checks for a JavaScript repository, running Prettier, type checking, and tests before each commit.
skill · ★ 302,251 · ↓ 489,289 · MIT
-
11. migrate-to-shoehorn
Replaces `as` type assertions in tests with helpers from `@total-typescript/shoehorn`. Use it when tests need partial objects or deliberately invalid data.
skill · ★ 302,251 · ↓ 475,388 · MIT
-
12. writing-plans
Creates an implementation plan from a spec before code changes begin. Use it when a task has multiple steps, files, and tests.
skill · ★ 304,495 · ↓ 282,859 · MIT
-
13. implement-spec
Implements a prepared spec from its ticket graph on one integration branch, using parallel subagents. Use it when tickets have blocking dependencies.
skill · ★ 302,251 · ↓ 283,700 · MIT
Testing skills ranked by repository stars and install counts, verified descriptions only. Check which runner a skill uses (pytest, Jest, Vitest, Playwright) and whether it runs the tests itself. Skip any skill that rewrites a failing test without looking for the cause. It is a plus when a skill can rerun a single failing test instead of the whole suite. To make sure tests always run, pair the skill with a hook: Claude Code hooks.
Other collections
- Best Claude Code skills
- Best Claude Code plugins
- Best Claude Code subagents
- Best Codex skills
- Best Cursor rules
- Best MCP servers
- MCP servers for Cursor
- Frontend skills
- Security skills and rules
- SEO and marketing skills
- Design skills
- DevOps skills
- MCP servers for databases
- Browser and scraping MCP servers