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.

Install to Claude Code

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