skills.rest
Uncodier
UncodierCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

makinari-test-orchestrator

Validate worker step outputs against test_results.json, GitHub SHAs, and preview URLs.

1|Updated May 8, 2025
Search Tags:#automation#workflow#testing#github#validation#qa#orchestrator
One-click install
npx skills add https://github.com/Uncodier/API --skill makinari-test-orchestrator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: makinari-test-orchestrator
Source: https://github.com/Uncodier/API/tree/main/src/skills/makinari-test-orchestrator
Command: npx skills add https://github.com/Uncodier/API --skill makinari-test-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill defines how to validate a worker step before the plan advances, using canonical test_results.json checks, GitHub SHA verification, and live preview URL validation to gate progression.

Core Features & Use Cases

  • Design plans with testing baked in: Include explicit testing instructions in each worker step to ensure verifiability.
  • Validate worker output after each step: Read test_results.json and ensure tests_failed equals 0 before proceeding.
  • Verify commit SHAs on GitHub & preview URL: Cross-check HEAD SHA and live deployment URL to confirm pushes succeed.
  • Final approval gating: Only approve deliveries when all checks pass and report status.

Quick Start

Create an instance_plan that includes per-step testing instructions and uses the test_results.json gating rules.

Frequently Asked Questions about makinari-test-orchestrator

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

FAQPage Schema
How do I validate worker steps and gate workflow progression using test results?▼

To validate worker steps, the orchestrator reads the canonical test_results.json file and ensures the tests_failed count is 0 before allowing the workflow to advance to the next phase.

What is the best way to automate end-to-end testing checks for orchestrated plans?▼

Automating end-to-end testing for orchestrated plans involves applying workflow guardrails by validating test_results.json, verifying commit SHAs on GitHub, and checking live preview URLs before progression.

How do I verify GitHub commit SHAs and preview URLs before approving a deployment?▼

You verify GitHub commit SHAs and preview URLs by cross-checking the HEAD SHA against GitHub and validating the live deployment URL to confirm pushes succeed before final approval gating triggers.

Can I include explicit testing instructions in each step of my instance plan?▼

Yes, you can design plans with testing baked in by including explicit testing instructions in each worker step within your instance_plan to ensure verifiability before progression.

Why does my workflow plan require explicit escalation for validation failures?▼

Your workflow plan requires explicit escalation for validation failures because the orchestrator enforces guardrails across the workflow, ensuring that a final approval trigger only occurs when all checks pass.

Related Skills

Explore More Software Engineering Skills→
UncodierUncodier

makinari-test-agent

Automates validation and testing of worker agents, emitting a standardized test_results.json artifact.

Community
Intermediate
Waterball-Software-AcademyWaterball-Software-Academy
77

aibdd-green-evaluate

Evaluate final acceptance suite reports for all-green PASS verdicts.

Official
Intermediate
Habitat-ThinkingHabitat-Thinking
44

github-actions-supply-chain

Assess GitHub Actions workflows for supply-chain security weaknesses.

Official
Intermediate
UncodierUncodier

makinari-fase-validacion

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

Community
Intermediate