repo-generating-validation-reports

What problem does it solve?

This Skill eliminates the risk of lost validation findings during long agent runs, inconsistent report naming across teams, and file collisions when running parallel validation or audit tasks across repository assets like documentation, CI configurations, and specifications.

Core Features & Use Cases

• Standardized 4-part report naming: Uses agent family, UUID chain, UTC+7 timestamp, and report type to ensure unique, consistent filenames across all runs.
• Progressive writing: Writes findings to the report file immediately during validation to prevent data loss from context compaction during long agent runs.
• Execution scope tracking: Enables parent-child workflow hierarchy tracing for multi-agent validation pipelines.
• Use Case: When running parallel docs-checker and readme-checker agents, this Skill ensures both generate unique, non-colliding reports, and all findings are preserved even if the agent context is compacted mid-validation.

Quick Start

Use the repo-generating-validation-reports skill to generate a validation report for the latest documentation changes, following the repository's naming and progressive writing standards.