Test Master

If you're spending time debating what to test or chasing flaky CI runs, this walks you through the whole testing lifecycle: scoping, strategy, writing tests with proper assertions, and reporting coverage gaps. It covers unit, integration, E2E, performance (k6), and security testing with OWASP methods. The quick-start example shows the pattern it enforces: meaningful descriptions, specific assertions, mocked dependencies. Includes reference docs for TDD iron laws and testing anti-patterns adapted from Jesse Vincent's work. The constraints section is blunt about what breaks tests in production: order dependencies, truthiness checks instead of specific assertions, ignoring error paths. Honestly, the structured approach helps most when onboarding junior developers or standardizing test quality across a team.

skills.sh installs: 5.7K
GitHub stars: 12.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add jeffallan/claude-skills --skill test-master --agent claude-code

Installs into .claude/skills of the current project.

Files

Test Master

Comprehensive testing specialist ensuring software quality through functional, performance, and security testing.

Core Workflow

Define scope — Identify what to test and which testing types apply
Create strategy — Plan the test approach across functional, performance, and security perspectives
Write tests — Implement tests with proper assertions (see example below)
Execute — Run tests and collect results
- If tests fail: classify the failure (assertion error vs. environment/flakiness), fix root cause, re-run
- If tests are flaky: isolate ordering dependencies, check async handling, add retry or stabilization logic
Report — Document findings with severity ratings and actionable fix recommendations
- Verify coverage targets are met before closing; flag gaps explicitly