aidex-coverage

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. Model-invocable since 2026-08-26 (decision/2026-08-26-coverage-canon-consolidation-and-targeted-runs.md, D1). Stack-agnostic since 2026-08-27 (decision/2026-08-27-aidex-is-stack-agnostic-stack-packs.md): 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 eval set in evals/ is owed a run against this description.

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. Per-project facts (ports, database names, commands, personas) live in that profile, never here — see 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.sh e2e/<spec>.spec.ts); the whole suite runs once, at plan close-out or pre-merge (D4). Measured before this rule: 32% of test runs inside unattended sessions were full suites, E2E at ~5 min each.

What this skill is not. It does not run an audit, does not build or read module-map.json or coverage-matrix.json, does not track a finding through its lifecycle, and does not carry the suite-speed measurement procedure. All of that is aidex-audit's test-coverage playbook (skills/aidex-audit/assets/templates/methodology/test-coverage.md.template). The split is by type, not by overlap: this skill owns the reference corpus and authoring rules — including the per-module judgment-pass checklist (references/06-judgment-pass.md) that the playbook's judged layer runs; the playbook owns inventory, finding lifecycle, matrix, sweep and escalation, and is the one that executes that checklist. The one rule with a foot in both — "a coverage percentage without a declared denominator is not a measurement" (m7) — is not duplicated: the playbook runs it as an inventory-time check ("is the denominator declared? can coverage even run?"), this skill states it as an authoring rule for anyone writing a new coverage-bearing test.