← ClaudeAtlas

cli-audit-testlisted

Audit test plan quality and maturity. Scores coverage, techniques, pyramid balance, negative testing, NFR, automation, CI integration. Use when reviewing a test plan, test strategy, test suite structure, or saying 'audit tests', 'test quality', 'test plan review', 'test maturity', 'are my tests good enough', 'test scoring', 'test pyramid'. Also triggers on 'test coverage', 'test gaps', 'missing tests'.
Destynova2/cli-code-skills · ★ 4 · Testing & QA · score 83
Install: claude install-skill Destynova2/cli-code-skills
> **Optimization:** This skill uses on-demand loading. Heavy content lives in `references/` and is loaded only when needed. > **Language rule:** Skill instructions are written in English. When generating user-facing output, detect the project's primary language (from README, comments, docs, commit messages) and produce the report in that language. If the project is bilingual, ask the user which language to use before proceeding. # Audit Test — Test Plan Quality & Maturity Scorer Evaluate a test plan or test suite against ISTQB standards, TMMi maturity model, and industry best practices. > "A test plan that only says 'we will test' without specifying *which techniques* and *why* is a major red flag." > — ISTQB Foundation Level Syllabus v4.0 ## Core Principle **A test plan is a contract with quality.** Every dimension left vague is a risk accepted silently. This skill measures how explicitly and completely that contract is defined, using a 12-dimension framework calibrated on ISTQB, TMMi, and proven industry patterns. ## Input `$ARGUMENTS` is the target to audit: - **Test plan document** (`.md`, `.txt`, `.adoc`, `.pdf`): audit the plan as written - **Tests directory** (`tests/`, `tests/e2e/`, etc.): infer the plan from the test structure, files, and config - **Empty**: search for test plans in the project root, then fall back to `tests/` directory analysis ### Input Discovery 1. Glob for test plan documents: `**/test-plan*`, `**/test-strategy*`, `**/TESTING*` 2. Glob