repo-generating-validation-reportslisted

# Generating Validation Reports Generate validation and audit reports following repository standards for naming, progressive writing, and UUID-based execution tracking. ## When This Skill Loads This Skill auto-loads for checker and fixer agents that need to generate validation reports in `generated-reports/`. ## Core Knowledge ### Report File Naming Pattern All reports follow the 4-part pattern: ``` {agent-family}__{uuid-chain}__{YYYY-MM-DD--HH-MM}__{type}.md ``` **Components**: - `{agent-family}`: Agent name WITHOUT `-checker` suffix (e.g., `docs`, `readme`, `plan`) - `{uuid-chain}`: Execution hierarchy as 6-char hex UUIDs separated by underscores - `{YYYY-MM-DD--HH-MM}`: UTC+7 timestamp (double dash between date and time) - `{type}`: Report type (`audit`, `validation`, `fix`) **Examples**: ``` generated-reports/docs__a1b2c3__2026-01-03--14-30__audit.md generated-reports/plan__d4e5f6__2026-01-03--15-00__validation.md generated-reports/demo-facts__a1b2c3_d4e5f6__2026-01-03--16-45__audit.md ``` ### UUID Generation Generate 6-character hexadecimal UUID at agent startup: ```bash MY_UUID=$(uuidgen | tr '[:upper:]' '[:lower:]' | head -c 6) # Example output: a1b2c3 ``` **Why 6 characters?** - 16^6 = 16,777,216 combinations - Collision probability for 1000 parallel executions: ~0.003% - Short for readability, long enough for uniqueness ### UUID Chain Logic **Scope-based execution tracking** enables parent-child hierarchy: **Tracking File Pattern**: `generated-repo