audit-validation

What problem does it solve?

It prevents wasted effort and incorrect plans by forcing verification of audit and codebase claims (e.g., missing files, LOC counts, duplicated patterns) against the actual repository state before you act on them.

Core Features & Use Cases

• Grep-first claim verification: checks existence, LOC, and pattern counts before using the audit’s assertions.
• Pattern shape confirmation: reads surrounding lines around representative matches to confirm the audit’s interpretation matches reality.
• Name and functionality cross-checking: searches for similarly named modules/components and for canonical call-site patterns when exact names may differ.
• Duplication validation: confirms duplication claims by locating duplication markers and sampling matches to ensure they’re truly duplicates.
• Discrepancy-aware planning: when verified measurements differ, the plan scope should record actual measurements and note mismatches instead of glossing over them.

Quick Start

Use the audit-validation skill when an input includes phrases like “the audit says,” “the analysis found,” or any “X is N LOC / Y doesn’t exist yet / this is duplicated across …” claim, and ask it to generate one-line shell verifications for each claim before writing a plan.