validate-report-file

Markdown report validation verifies the presence of mandatory sections like Header, Executive Summary, and Detailed Findings. It applies a defined schema to enforce header metadata presence, section consistency, and status alignment, ensuring reports meet structural requirements before downstream processing or submission.

Yes, you can use a report completeness check as a CI/CD quality gate to automatically reject incomplete or malformed markdown reports. This prevents downstream issues by verifying formatting rules, heading structures, and status consistency before allowing further processing.

Formatting validation in markdown reports enforces rules for headings, status indicators, and code blocks. It ensures logical alignment between the header status and validation outcomes, applying strict quality checks to prevent structural inconsistencies in agent-generated report files.

Debugging missing sections in markdown reports involves running a structural validation against a defined schema. This process identifies absent mandatory sections like Validation Results or Next Steps, checks header metadata, and flags status indicator inconsistencies for correction.

Yes, report auditing requires adherence to a defined schema for header metadata, section presence, and status consistency. This schema-driven approach ensures the validation process can accurately verify formatting rules and logical alignment within agent-generated markdown reports.