test-harness-auditor

# Test Harness Auditor Audit any repo's feedback infrastructure across six layers and generate optimized configs for AI coding agents. ## When to Run - Entering a new repo with no `.claude/lint-rules.json` - User asks to audit tests, lint setup, or agent infrastructure - After cloning a repo to check what feedback loops exist - Periodically to catch configuration drift ## Two-Phase Workflow ### Phase 1: Audit (read-only) Run the audit script to scan the current repo: ```bash uv run ~/.claude/skills/test-harness-auditor/scripts/audit.py ``` Or target a specific directory: ```bash uv run ~/.claude/skills/test-harness-auditor/scripts/audit.py /path/to/repo ``` For machine-readable output (consumed by Phase 2): ```bash uv run ~/.claude/skills/test-harness-auditor/scripts/audit.py --json > /tmp/audit.json ``` To save a snapshot for drift detection (tracks score changes over time): ```bash uv run ~/.claude/skills/test-harness-auditor/scripts/audit.py --save ``` Combine flags: `--json --save` saves the snapshot AND outputs JSON. On subsequent `--save` runs, the report includes a drift section showing score regressions, config changes, and residue file changes. The script produces a structured Markdown report (or JSON with `--json`) with: - **Stack summary**: detected language, frameworks, package manager, actual scripts from package.json - **Scorecard**: 0-3 score for each of the six layers (test, lint, type-check, SA, build, debug) - **Findings**: per-layer details o...