validate-build

Restore, build, and test repositories with structured pass/fail reports.

11|4|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/MostAshraf/ai-sdlc-harness --skill validate-build-mostashraf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-build
Source: https://github.com/MostAshraf/ai-sdlc-harness/tree/main/skills/validate-build
Command: npx skills add https://github.com/MostAshraf/ai-sdlc-harness --skill validate-build-mostashraf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables automated, language-agnostic build and test validation across a repository by reading per-repo configuration and executing a restore/build/test cycle, then reporting structured results.

Core Features & Use Cases

  • Read per-repo language-config.md to determine project roots and commands.
  • Execute restore, build, and test steps and parse outputs with configured patterns.
  • Produce a structured report with pass/fail status and detailed error/test summaries.

Quick Start

Run /validate-build on a target repository to perform restore, build, and test validation.

Frequently Asked Questions about validate-build

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

FAQPage Schema
How do I automate build and test validation across multiple programming languages in CI?

Automated build and test validation across multiple languages is achieved by reading a per-repository language configuration file to determine project roots, then orchestrating a complete restore, build, and test cycle language-agnostically.

How do I parse CI test output using custom regex patterns to surface build failures?

Parsing CI test output with custom regex patterns involves executing build and test steps, then correlating command outputs against repository-configured regex patterns to produce a structured pass/fail report and surface top errors.

What is the best way to generate a structured pass/fail report for automation dashboards?

Generating a structured pass/fail report for automation dashboards requires parsing command outputs against configured regex patterns after running a restore, build, and test cycle, resulting in detailed error and test failure summaries.

Does this build validation approach work without hardcoding language-specific commands?

Yes, this build validation approach works without hardcoding commands by loading per-repo configuration from a language configuration file to determine project roots and commands, operating language-agnostically across supported languages.

How do I run an end-to-end restore, build, and test cycle on a target repository?

Running an end-to-end restore, build, and test cycle on a target repository involves reading the repository's language configuration to identify commands, executing the cycle, and parsing outputs with configured patterns to report results.

Why do I need a language-config.md file for automated test validation?

A language configuration file is needed for automated test validation because it determines project roots and specific commands required to execute the restore, build, and test cycle language-agnostically across the repository.