makinari-fase-validacion

Validate frontend and backend builds produce required artifacts and test_results.json.

1|Updated May 8, 2025
One-click install
npx skills add https://github.com/Uncodier/API --skill makinari-fase-validacion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: makinari-fase-validacion
Source: https://github.com/Uncodier/API/tree/main/src/skills/makinari-fase-validacion
Command: npx skills add https://github.com/Uncodier/API --skill makinari-fase-validacion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that software builds complete successfully and essential artifacts (test_results.json) are produced and ready for gate automation.

Core Features & Use Cases

  • End-to-end validation of frontend and backend components
  • Ensures presence and integrity of the canonical test_results.json artifact
  • Produces evidence for the automated gate and delegates backlog decision to makinari-rol-judge
  • Supports deterministic verification via the provided harness

Quick Start

Trigger the validation phase using the harness to run builds, tests, and artifact checks.

Frequently Asked Questions about makinari-fase-validacion

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

FAQPage Schema
How do I validate frontend and backend builds before deploying artifacts in CI/CD?

To validate builds in CI/CD, you can trigger a validation harness that checks frontend and backend components, confirms artifact publication, and records results for gate automation.

How do I generate test_results.json for automated gate evaluation?

Generating test_results.json requires a validation harness that runs builds and tests, records the validation outcomes, and writes them into the file for governance review.

What is build validation in the context of artifact management and gate automation?

Build validation for artifact management is the process of verifying that builds complete successfully and produce required artifacts like test_results.json for an automated gate to consume.

Does build validation require any specific dependencies to verify artifact integrity?

Build validation requires no specific external dependencies to verify artifact integrity, relying on a provided deterministic harness to confirm artifact presence and availability for gate consumption.

When should I use an automated validation harness instead of manual build checks?

An automated validation harness should be used when you need deterministic verification of frontend and backend builds, ensuring artifacts are published and test_results.json is generated for subsequent gate steps.

Why does my automated gate fail to find the required build artifacts?

An automated gate fails to find build artifacts when the validation harness does not complete successfully or lacks the mechanism to publish the artifact and write the required test_results.json file.