Skip to main content
affpapa.org
RU EN
skill CX Codex

testing-strategies · akillness — Claude Code skill: what it does, install

This skill turns unclear test policy into a focused validation brief. Use it to choose the gate, risk level, and evidence a change needs.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add akillness/jeo-skills --skill testing-strategies -a claude-code
Open on GitHub

What testing-strategies does

testing-strategies takes a change, gate-design, flaky-suite, release-readiness, or incident packet and turns it into a testing decision. It identifies whether the real question concerns merge blocking, release proof, or scheduled coverage. It then picks one policy mode, classifies the change risk, and selects the smallest convincing mix of validation layers.

The skill separates local, PR, release, and scheduled expectations. It also gives structure to decisions about noisy or costly suites and routes implementation, debugging, review, accessibility, deployment, or performance work to a more suitable skill. It fits CLI/dev workflow and backend, frontend, or fullstack repositories. It is not for writing stack-specific tests, isolating a failing test, or reviewing a line-by-line diff.

What it helps with

  • choose validation for an API change or database migration
  • separate local, PR, release, and scheduled checks
  • decide whether a flaky suite should block or move
  • define lasting regression coverage after an incident
  • route test implementation away from policy design

Example prompts for the agent

  • Create a validation brief for this API change and database migration.
  • Decide which checks should block the PR and which belong to release or scheduled runs.
  • Review this flaky suite and classify what should block, move, or become informational.

How to install testing-strategies

1Skills CLI (Vercel)

npx skills add akillness/jeo-skills --skill testing-strategies -a claude-code

2Manually: put the files in place

~/.claude/skills/testing-strategies/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/testing-strategies/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about testing-strategies

How do I install testing-strategies in Claude Code?

Run npx skills add akillness/jeo-skills --skill testing-strategies -a claude-code, then check ~/.claude/skills/testing-strategies/SKILL.md.

What does testing-strategies do?

It turns a change or test-policy dispute into a validation brief with a named gate, one primary policy mode, a risk tier, and a focused evidence plan.

Is testing-strategies meant to write tests?

No. It handles policy and validation choices, while stack-specific test implementation, failure debugging, and line-by-line review belong elsewhere.

Similar skills

All skills for Testing and QA →

testing-strategies by other authors comes first.

testing-strategies c0x12c Gives your coding agent ready test patterns for a Micronaut and Kotlin backend: integration tests, repository tests, test data builders. CX Codex +1 ★ 109repo stars improve-codebase-architecture Matt Pocock This skill scans a codebase for architectural friction, then builds a visual HTML report with refactoring candidates. Use it before a deeper architecture review. 1,163,035installs design-taste-frontend Leonxlnx This skill directs the design of public pages and work screens, then checks the result in a browser through screenshots. Use it when an interface feels generic or unfinished. CX Codex +1 678,700installs tdd Matt Pocock Guides the red-green TDD loop: ensures tests are written first, keep them at public interfaces, and avoid coupling to implementation details. 1,141,062installs skill-creator official anthropics Creates and refines skills, then tests them with prompts, evaluations, and performance checks. 414,180installs agent-browser vercel-labs A CLI skill for browser control: it opens pages, fills forms, clicks buttons, and tests web apps. Use it when an agent needs to act inside a website. CX Codex +1 1,200,000installs prototype Matt Pocock Creates throwaway prototypes for checking state logic or exploring UI before committing the decision to the main codebase. 986,201installs

From the same set46

log-analysis A skill that reads runtime logs: it picks one evidence packet first, then isolates the earliest failure. Useful when the log is long and you need the one line that matters. CX Codex +1 384installs plannotator The skill opens a browser approval loop: a human reads a plan, diff or spec and leaves notes before any code gets written. CX Codex +1 379installs marketing-automation The skill turns a vague marketing request into one operating mode, one discipline and one operator packet with an owner and proof. CX Codex +1 377installs monitoring-observability Turns service, data-pipeline, or live-ops context into a monitoring brief with a primary mode, useful signals, and a small first implementation slice. CX Codex +1 369installs authentication-setup Walks you through choosing an auth lane for a web app or API and drawing the line between what the provider owns and what stays in your app. CX Codex +1 368installs changelog-maintenance This skill turns verified shipped work into changelog entries, release notes, migration updates, and small game patch notes. Use it after a release or patch. CX Codex +1 367installs bmad-idea Turns a rough idea into a single concept artifact and points to the next skill. Meant for the step before PRDs and sprint plans. CX Codex +1 366installs security-best-practices This skill turns vague web and API security requests into one scoped hardening brief, with a primary risk area and matching verification steps. CX Codex +1 366installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor