write-validation-report

Aggregate validation results into a dated pass/fail Markdown report.

1|Updated Nov 19, 2025

Search Tags:#automation #testing #markdown #validation #qa #report #ci

Ready to run

npx skills add https://github.com/MihaiOnSoftware/.ai --skill write-validation-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-validation-report
Source: https://github.com/MihaiOnSoftware/.ai/tree/main/skills/write-validation-report
Command: npx skills add https://github.com/MihaiOnSoftware/.ai --skill write-validation-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of standardized validation reports by aggregating validation results into a Markdown document, saving time and ensuring consistency across teams.

Core Features & Use Cases

Automatically assemble validation details into a well-formatted Markdown report.
Enforce a consistent naming scheme and storage location for reports.
Suitable for QA testing, CI validation, and manual validation workflows where fast, repeatable reporting is needed.

Quick Start

Use the write-validation-report.sh script to generate a new report by piping your content into the tool:

cat <<EOF | ~/.ai/scripts/generic/write-validation-report.sh <report_being_validated> <pass|fail> [date] <report_content> EOF

Frequently Asked Questions about write-validation-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a standardized validation report in Markdown for QA testing?▼

To generate a standardized validation report in Markdown, you can pipe your validation results into a shell script that aggregates the content and outputs a dated pass/fail file. This ensures consistent formatting and storage location for QA testing workflows.

What is the best way to automate validation report creation in a CI pipeline?▼

Automating validation report creation in a CI pipeline involves executing a shell script that aggregates validation results into a Markdown document. The script enforces a consistent naming scheme and outputs a dated pass/fail report at an expected path.

How do I format manual validation checks into a consistent pass/fail Markdown document?▼

Formatting manual validation checks into a pass/fail Markdown document is done by piping the check results into a dedicated script. The script processes the input content and generates a well-formatted, dated Markdown report at a standardized location.

Can I use a shell script to aggregate CI validation results into a single report?▼

Yes, you can use a shell script to aggregate CI validation results into a single report. The script takes piped content, a report name, and a pass/fail status to produce a standardized, dated Markdown file for consistent CI validation tracking.

Does generating a validation report require any external dependencies?▼

Generating a validation report with this method requires no external dependencies, relying solely on a standard shell script. It operates independently to aggregate content and output a Markdown validation report, making it lightweight for CI and QA environments.

Why should I use a standardized script for validation reporting instead of writing Markdown manually?▼

Using a standardized script for validation reporting enforces a consistent naming scheme and storage location, saving time across teams. It prevents formatting discrepancies by automatically assembling validation details into a well-formatted, dated Markdown document.