Ln 630 Test Auditor
Use when auditing the test surface through the evaluation platform with mandatory research, coordinated test audit workers, and structured summaries.
MCP get_skill({ skillId: "test-auditor-453ce832" })Use this skill with your agent
Create a free account and connect via MCP
> **Paths:** File paths (`references/`, `../ln-*`) are relative to this skill directory.
**Type:** L2 Coordinator
**Category:** 6XX Audit
# Test Auditor
## Mandatory Read
**MANDATORY READ:** Load `references/evaluation_coordinator_runtime_contract.md`, `references/evaluation_summary_contract.md`, `references/evaluation_research_contract.md`
**MANDATORY READ:** Load `references/audit_final_report_contract.md`
**MANDATORY READ:** Load `references/test_audit_worker_boundaries.md`
**MANDATORY READ:** Load `references/risk_based_testing_guide.md`, `references/research_tool_fallback.md`
Conditional read: load `references/risk_based_testing_methodology.md` only when worker findings require full methodology examples or anti-pattern detail.
Conditional read: load `references/epistemic_protocol.md` only when source confidence or claim uncertainty affects issue validation.
## Purpose
- audit test-suite value through independent worker angles: product behavior, E2E journeys, portfolio value, critical coverage, trustworthiness, manual evidence, structure, and oracle strength
- coordinate `ln-631` through `ln-638`
- require current testing best-practice research
## Runtime Contract
Runtime family:
- `evaluation-runtime`
Identifier:
- `test-audit`
Phase order:
1. `PHASE_0_CONFIG`
2. `PHASE_1_DISCOVERY`
3. `PHASE_2_RESEARCH`
4. `PHASE_3_DELEGATE`
5. `PHASE_4_AGGREGATE`
6. `PHASE_5_REPORT`
7. `PHASE_6_SELF_CHECK`
## Worker Set
- `ln-631-test-business-logic-auditor`
- `ln-632-test-e2e-priority-auditor`
- `ln-633-test-value-auditor`
- `ln-634-test-coverage-auditor`
- `ln-635-test-isolation-auditor`
- `ln-636-manual-test-auditor`
- `ln-637-test-structure-auditor`
- `ln-638-test-oracle-effectiveness-auditor`
## Worker Invocation (MANDATORY)
**Host Skill Invocation:** `Skill(skill: "...", args: "...")` is mandatory delegation.
- Claude: call the Skill tool exactly as shown.
- Codex: if no Skill tool exists, locate the named skill in available skills, read its `SKILL.md`, treat `args` as `$ARGUMENTS`, execute that skill workflow, then return here with its result/artifact.
- Do not inline worker logic or mark the worker complete without executing the target skill.
Use the Skill tool for delegated workers. Do not inline worker logic inside the coordinator.
TodoWrite format (mandatory):
- `Resolve audit scope and build manifest`
- `Load test infrastructure and coverage`
- `Run best-practice research`
- `Delegate to domain audit workers`
- `Aggregate worker findings`
- `Generate final audit report and remediation plan`
- `Verify cleanup and self-check`
Representative invocations:
```text
Skill(skill: "ln-631-test-business-logic-auditor", args: "{scope}")
Skill(skill: "ln-632-test-e2e-priority-auditor", args: "{scope}")
Skill(skill: "ln-633-test-value-auditor", args: "{scope}")
Skill(skill: "ln-634-test-coverage-auditor", args: "{scope}")
Skill(skill: "ln-635-test-isolation-auditor", args: "{scope}")
Skill(skill: "ln-636-manual-test-auditor", args: "{scope}")
Skill(skill: "ln-637-test-structure-auditor", args: "{scope}")
Skill(skill: "ln-638-test-oracle-effectiveness-auditor", args: "{scope}")
```
## Workflow
1. Start `evaluation-runtime`.
2. Discover automated and manual test surfaces.
3. Perform mandatory research.
4. Delegate audit workers.
5. Aggregate findings into one risk-based test audit by reading every worker `report_path`, normalizing actions from `references/test_audit_worker_boundaries.md`, deduplicating issues, resolving worker conflicts, and validating actionable problems against `references/evaluation_research_contract.md`.
6. Write `.hex-skills/runtime-artifacts/runs/{run_id}/audit-report/ln-630--final-report.md` with remediation plan per `references/audit_final_report_contract.md`.
7. Include final pruning groups: delete low-value tests, merge duplicates, rewrite to product behavior, add missing risk-based tests, and keep high-value regression/business-risk tests.
8. Remove temporary worker markdown reports and record cleanup evidence.
9. Write the `evaluation-coordinator` summary with `report_path` set to the final report.
## Definition of Done
- [ ] Evaluation runtime started
- [ ] Test surfaces discovered
- [ ] Mandatory research completed
- [ ] All planned worker summaries recorded
- [ ] Worker conflicts resolved with `test_audit_worker_boundaries.md`
- [ ] Final report and remediation plan written
- [ ] Temporary worker markdown reports removed
- [ ] `evaluation-coordinator` summary written
- [ ] Runtime completed
## Meta-Analysis
Optional reference: load `references/meta_analysis_protocol.md` only when the user asks for post-run meta-analysis or protocol-formatted run reflection.
When requested after the coordinator run, analyze the session per protocol section 7 and include the protocol-formatted output with the final test audit result.
## References
- Workers: `../ln-631-test-business-logic-auditor/SKILL.md`, `../ln-632-test-e2e-priority-auditor/SKILL.md`, `../ln-633-test-value-auditor/SKILL.md`, `../ln-634-test-coverage-auditor/SKILL.md`, `../ln-635-test-isolation-auditor/SKILL.md`, `../ln-636-manual-test-auditor/SKILL.md`, `../ln-637-test-structure-auditor/SKILL.md`, `../ln-638-test-oracle-effectiveness-auditor/SKILL.md`
---
**Version:** 4.0.0
**Last Updated:** 2025-12-23Related Skills
More skills in Software Engineering
Accessibility Standards
Comprehensive web accessibility standards based on WCAG 2.2 AA, with 38+ anti-patterns, legal enforcement context (EAA, ADA Title II), WAI-ARIA patterns, and framework-specific fixes for modern web frameworks and libraries.
Accord
Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria). No code. Use when authoring cross-team specs, building L0-L3 packages, or aligning Biz/Dev/Design on a single source of truth.
Acquire Codebase Knowledge
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
Acreadiness Assess
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
Acreadiness Generate Instructions
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
Acreadiness Policy
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
Explore Other Categories
Skills from other categories with shared topics
Ln 014 Agent Instructions Manager
Creates AGENTS.md canonical and CLAUDE.md @AGENTS.md stub; audits token budget, cache safety, import-pattern compliance. Use when instruction files need alignment.
Ln 022 Researchgraph
Indexes and queries project research graphs backed by hex-research MCP. Use for hypotheses, goals, benchmark runs, evidence depth, derived goal metrics, lineage, generated research maps, and graph audits.
Ln 100 Documents Pipeline
Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.