test-audit-implementer

Execute phased test-audit plans with per-phase commits and progress tracking.

Updated Apr 27, 2026

Search Tags:#testing #audit #fixtures #progress-tracking #test-suite #phased-approach #incremental-commits

Ready to run

npx skills add https://github.com/chrisdavidmiles/claude-skills --skill test-audit-implementer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-audit-implementer
Source: https://github.com/chrisdavidmiles/claude-skills/tree/main/skills/test-audit-implementer
Command: npx skills add https://github.com/chrisdavidmiles/claude-skills --skill test-audit-implementer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It automates phased test-audit execution by applying audit directives incrementally, ensuring safe commits and progress tracking through TEST_AUDIT_PROGRESS.md.

Core Features & Use Cases

Phase-based execution of TEST_AUDIT.md plans with per-phase commits.
Surface unexpected findings and enforce real fixtures, not fabricated data.
Do not write tests for production code that doesn't exist; surface fictional-feature findings and track decisions for product changes.

Quick Start

Read TEST_AUDIT.md, initialize progress tracking, and begin Phase 0 setup by running the test suite and creating a progress log.

Frequently Asked Questions about test-audit-implementer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I execute a test audit plan phase-by-phase with safe commits?▼

Executing a test audit plan phase-by-phase involves applying audit directives incrementally and creating per-phase commits. This approach ensures safe version control while tracking progress in a dedicated log file.

What is the best way to track test audit progress in a software project?▼

The best way to track test audit progress is by using an automated progress log file. This file records completed phases, unexpected findings, and product decisions surfaced during the audit execution.

How do I prevent fabricated test fixtures during an automated test audit?▼

To prevent fabricated test fixtures during an automated test audit, the execution process enforces non-fabrication rules. It verifies production code presence before adding tests to ensure data integrity.

What should I do if my test audit finds tests for production code that doesn't exist?▼

If a test audit finds tests for production code that does not exist, it surfaces these fictional-feature findings in a structured way. This tracks necessary product decisions rather than writing missing code blindly.

Do I need a TEST_AUDIT.md plan to start an incremental test audit?▼

Yes, you need a TEST_AUDIT.md plan to start an incremental test audit. The automated execution process applies the directives defined in this file sequentially across multiple phases.