Testing Strategies

This one cuts through "we need more tests" fog and gets you to a real decision: what gate are you actually designing, what risk tier is the change, and what's the minimum layer mix that proves it. It routes you out fast if the work is really implementation, debugging, or code review instead of policy. The packet normalization is smart: change-risk, gate-design, flake-cost, release-readiness, or incident-ratchet. You get a structured way to separate PR blockers from release smoke from scheduled breadth, which saves teams from treating protected branch tooling like a complete strategy. Use it when the conversation is stuck on confidence levels and handoff boundaries, not when you just need to write the actual tests.

skills.sh installs: 173
GitHub stars: 22
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add akillness/oh-my-skills --skill testing-strategies --agent claude-code

Installs into .claude/skills of the current project.

Files

Testing Strategies

Use this skill when the main question is "what validation packet do we trust, what confidence level do we actually need, and what should the team do next?"

The job is not to dump a generic pyramid/trophy manifesto or write test code. The job is to:

normalize the current policy packet,
name which gate is actually being decided,
choose one primary policy mode,
name the smallest convincing layer mix,
separate local / PR / release / scheduled expectations,
state exception and flake rules honestly,
route implementation, debugging, release execution, accessibility, game launch, or performance work out immediately.

SKILL.md on GitHub

Sponsors

Promote your product hereReach 125k+ visitors monthly Promote your product hereReach 125k+ visitors monthly