testslisted

Fixes failing tests and lint/type errors, audits test-suite quality with a fleet of specialist reviewers, or drives coverage — for any project configured with a supermodo skills.config.json. Modes: `tests` (default) fixes every failure tier by tier (unit, integration, E2E, lint); `tests audit [scope]` spawns parallel specialist reviewers (spec-alignment, assertion-strength, corner-cases, coverage-balance, and a domain lens derived from the project's docs), runs mutation probes where configured, and adversarially verifies every finding with a second model before reporting; `tests coverage` drives coverage to the configured target with a balance check. Use whenever the user mentions failing tests, lint errors, "make tests pass", green build, flaky tests, test quality, weak or missing tests, corner cases, coverage, mutation testing, or asks whether the tests actually protect the core logic — even without "/tests".
supermodo/skills · ★ 1 · Testing & QA · score 77

Install: claude install-skill supermodo/skills

# tests — fix, audit, coverage > **Requires:** the sibling `protocols` skill (shared protocol masters) and a valid `skills.config.json` (create with the `config` skill). Missing either → halt with that exact pointer; never guess. Test coordinator for a supermodo-configured project. All framework, command, and domain specifics come from `skills.config.json` and the project's docs — nothing about a stack is hardcoded here. > **Cross-tool note (Claude Code ↔ Codex).** Written in Claude Code idioms. Under > Codex, translate: `AskUserQuestion` → ask in chat; `Agent`/`subagent_type` → > your native delegation; `TaskCreate`/`TaskList`/`TaskUpdate` → your own task > tracking. Audit verification uses the OTHER provider as the adversary — under > Claude the adversary is `codex exec`, under Codex it is `claude -p` (see > `../protocols/references/cross-model.md`). Invert accordingly so the second model is > genuinely different. ## 0. Preflight — config first Read and validate `skills.config.json` per `../protocols/references/config.md` BEFORE acting (run the `config` skill's `../config/scripts/config-check.ts` or apply its rules). Missing/invalid config → halt naming the field, point at `config`. Wrong `configVersion` → halt per the version rule. **Commands come only from `commands.*`** (argv arrays, executed without a shell; first use of each in a session shown to the user and explicitly approved per `../protocols/references/config.md`). Resolve the tiers you need: | Tier