skills.rest
Imad-Oute
Imad-OuteCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

mh-ms-validator

Validate MicroHard artifact builds against predefined conventions and generate PASS/FAIL reports.

2|Updated Apr 5, 2026
Search Tags:#quality assurance#code review#build validation#validation report#MicroHard
One-click install
npx skills add https://github.com/Imad-Oute/MicroHard --skill mh-ms-validator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mh-ms-validator
Source: https://github.com/Imad-Oute/MicroHard/tree/main/src/modules/ms/4-review/mh-ms-validator
Command: npx skills add https://github.com/Imad-Oute/MicroHard --skill mh-ms-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that MicroHard artifact builds adhere to predefined conventions, helping maintain quality and integrity throughout the development lifecycle.

Core Features & Use Cases

  • Comprehensive Validation: Validates naming, frontmatter, I/O contracts, step linkage, and completeness of built files.
  • Automatic Reporting: Generates a detailed validation report indicating PASS/FAIL results for each check.
  • Integrates with Workflow: Designed to follow the 'mh-ms-file-engineer' Skill in the build workflow, ensuring artifacts are thoroughly reviewed before deployment.

Quick Start

Run the 'ms validate' command after the build process to check the artifact's quality and receive a validation report.

Frequently Asked Questions about mh-ms-validator

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

FAQPage Schema
How do I validate MicroHard artifact builds against coding conventions?▼

To validate MicroHard artifact builds, you run the 'ms validate' command, which checks naming, frontmatter, I/O contracts, and file completeness against internal library references. It generates a detailed PASS/FAIL report ensuring quality before deployment.

What does a MicroHard build validation report include?▼

A MicroHard build validation report includes comprehensive PASS/FAIL results for each convention check. It specifically covers artifact naming, frontmatter structure, I/O contracts, step linkage, and the completeness of built files to ensure structural integrity.

Do I need to run the mh-ms-file-engineer Skill before validating MicroHard artifacts?▼

Yes, you need to run the mh-ms-file-engineer Skill first to build the artifacts. The validator is designed to follow this step in the workflow, ensuring the generated files are reviewed against conventions before deployment.

What environment is required to check MicroHard artifact quality before deployment?▼

Checking MicroHard artifact quality requires a structured environment with direct access to artifact build paths and output report directories. This setup allows the validation scripts to read built files and generate accurate quality assessments.

Why does my MicroHard artifact validation report show a FAIL status?▼

A validation report shows a FAIL status when built MicroHard artifacts violate predefined conventions. The validator checks frontmatter formatting, I/O contracts, naming rules, and step linkage, indicating exactly which quality checks were not met.

Related Skills

Explore More Software Engineering Skills→
Imad-OuteImad-Oute
2

mh-ms-concept-engineer

Convert raw ideas into structured artifact-brief.md specifications for MicroHard projects.

Community
Intermediate
pixel-cellarpixel-cellar
277

gate-check

Validate required artifacts and stage gates to output PASS/CONCERNS/FAIL results.

Official
Intermediate
magnus919magnus919
86

architect-pyramid

Map C4 views, ADRs, and arc42 constraints into a unified artifact pyramid.

Community
Advanced
OreStudioOreStudio
25

domain-type-creator

Scaffold domain types with JSON I/O, table I/O, and repository support.

Official
Basic