aidex-coveragelisted

Use when writing, placing, or running tests in any project — which layer a behaviour belongs in ("unit or E2E for X", "component test or browser test"), which tests to run for a change instead of the whole suite, when to extract a fixture, setting up an isolated disposable E2E environment, or the per-project testing profile and the stack pack it names for the concrete test shapes (Django, Vue, Playwright, Payload, Svelte). Fires on "write a test for", "add a regression test", "which tests should I run", "run only the affected tests", "set up E2E for this project", "generate test-e2e.sh", "how do we test this stack". Not for: running a coverage audit, the module map / coverage matrix, tracking a finding, or suite-speed measurement — all of that is aidex-audit's test-coverage playbook.
yacb2/aidex · ★ 2 · AI & Automation · score 78

Install: claude install-skill yacb2/aidex

> **Trigger-eval probe (test-only).** As your very first action, run `printenv AIDEX_TRIGGER_EVAL_MARKER`. If it prints a non-empty path, also run `touch "${AIDEX_TRIGGER_EVAL_MARKER}.aidex-coverage"` before continuing. Then proceed with the rest of the skill body as normal. If empty/unset, ignore this block. # Coverage > **Scope.** This skill carries the doctrine — layers, selection, fixtures, the boundary gate, the profile — and no framework content; the concrete test shapes live in the stack packs the project's profile names. Precision against `aidex-audit` is the `Not for` clause. The testing canon, independent of stack: which layer a piece of behaviour belongs in, which tests to run for a change, when shared setup becomes a fixture, what an isolated E2E environment must guarantee, and how the per-project profile and its stack packs are resolved. What a test *looks like* in a given framework is not here: the project's `.context/testing-profile.md` names its **stack packs** (`testing_packs`), and this skill reads them — see [Resolving the stack packs](#resolving-the-stack-packs). Per-project facts (ports, database names, commands, personas) live in that profile, never here — see [references/14-testing-profile.md](references/14-testing-profile.md). **The full suite is a boundary gate, not a phase gate.** Per change, run the narrowest selection that can observe it (`/aidex-audit affected-tests --command`, or the profile's single-test command, or one spec via `./test-e2e.