Testing & Quality skills

Browse reusable Agent Skills, each with a clear purpose and practical guidance.

cd-test-architecture

Evaluate an existing application's tests and recommend a CD-pipeline-aligned test architecture — fast, deterministic tests with minimal tooling that fully validate behavior (including cross-service interaction) and run in CI without configuring the rest of the system. Use when the user says "evaluate how this app is tested", "design a test architecture", "align our tests for CD", "make our CI tests deterministic", "our tests need the whole system configured", "our tests live in another repo / Postman / manual scripts", or asks for UI/service/batch test patterns.

252 repo starsObserved in 1 repos

Testing & Quality

GitHub

co-evolution-audit

Flag production files that churn repeatedly while their paired test files do not change — the "Red Queen" co-evolution gap. Uses git log --stat to compute per-file change frequency over a configurable window, applies language-aware pairing heuristics (Python, JS/TS, Go, Java, C#), and produces a ranked table of stale-coverage pairs. Feeds test-health and test-improve as prioritization input, not a standalone gate. Use when you want to find high-churn files whose tests have gone stale, or before running /test-improve to identify the highest- leverage targets first.

252 repo starsObserved in 1 repos

Testing & Quality

GitHub

coverage-baseline

Multi-workflow coverage baseline worker. Detects the repo's coverage tool from its build manifest, runs it, records the resulting line+branch percentages as the baseline, and posts the number to the parent issue (or local `FEATURE.md`). This number is the floor every later phase must improve on. Called by `/test-improve` (Phase 2) via `--workflow test-improve`.

252 repo starsObserved in 1 repos

Testing & Quality

GitHub

coverage-delta

Multi-workflow coverage delta worker. Reads the baseline coverage, re-runs the same coverage tool against the current suite, computes the delta on line+branch percentages, and posts it to the parent issue (or local `FEATURE.md`). Called after each Story so the operator sees coverage move with every test added. Called by `/test-improve` (Phase 4) via `--workflow test-improve`.

252 repo starsObserved in 1 repos

Testing & Quality

GitHub

exploratory-testing

Charter-driven exploratory testing — probe a running feature/endpoint with structured heuristics, evaluate charter quality, run adversarial expansion, classify defects, and auto-triage critical findings into an incremental report. Use when the user runs /explore, says "explore this endpoint", "poke at this feature", "find bugs in the running app", or wants hands-off exploratory testing of a live target.

252 repo starsObserved in 1 repos

Testing & Quality

GitHub

false-positive-reduction

Hybrid FP-reduction — joern when present, LLM fallback when absent. Six-stage rubric (Stage 0 + Stages 1-5) applied to every finding; emits the disposition register.

252 repo starsObserved in 1 repos

Testing & Quality

GitHub

farley-score

Evaluate test quality using Dave Farley's 8 properties with a weighted Farley Score. Use when reviewing test suites, after writing tests, or when the user says "score my tests", "test quality", "Farley score", or "how good are my tests".

252 repo starsObserved in 1 repos

Testing & Quality

GitHub

feature-file-validation

Validate Gherkin feature files for structural quality, determinism, and implementation independence, then verify each scenario has matching test automation. Use this skill whenever reviewing test files, feature files, or BDD scenarios — including during /code-review when .feature files or step definition files appear in the changeset. Also use when a user asks to "check my feature files", "validate my Gherkin", "are my scenarios testable", or "do my feature files have tests".

252 repo starsObserved in 1 repos

Testing & Quality

GitHub

fix-with-phpstan

Fix PHPStan static analysis errors in PHP files. Use this skill whenever the user asks to "fix PHPStan errors", "run PHPStan on", or "clean up types in" one or more PHP files or a module directory.

252 repo starsObserved in 1 repos

Testing & Quality

GitHub

gherkin-derive

Derive Gherkin scenarios directly from a codebase — standalone, with no prior legacy-modernization analysis. Discovers the public surface (OpenAPI, routes, existing tests, then exported signatures), recommends a BDD binding mode via the bdd-value-guide rubric, and writes `.feature` files plus (in bdd-runner mode) pending step-definition stubs. Use it on its own to capture intended behavior before changing tests, or as Phase 2b of `/test-improve`. Creates no tracker Stories.

252 repo starsObserved in 1 repos

Testing & Quality

GitHub