validation

Register shell commands as named validation steps for CI-style workflows.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/mecolejr/EVL-mOC5 --skill validation-mecolejr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validation
Source: https://github.com/mecolejr/EVL-mOC5/tree/main/.local/skills/validation
Command: npx skills add https://github.com/mecolejr/EVL-mOC5 --skill validation-mecolejr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Registers shell commands as named validation steps (lint, test, typecheck, etc.) that can be triggered and monitored to verify code quality.

Core Features & Use Cases

  • Create or update named validation commands with upsert behavior.
  • Run validation commands and monitor results in CI-style workflows.
  • Fetch run details, stop runs, and manage validation tasks across a team's codebase.

Quick Start

Configure a named validation command with setValidationCommand, then start a run with startValidationRun to execute all checks.

Frequently Asked Questions about validation

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

FAQPage Schema
How do I register shell commands as named validation steps for CI workflows?

You can register shell commands as named validation steps using an upsert function, allowing you to create or update checks like lint and test commands. These steps can then be triggered and monitored in CI-style workflows to verify code quality.

How do I run and monitor validation commands after feature work?

To run validation commands after feature work, start a validation run to execute all registered checks. You can monitor the run results, fetch run details, or stop active runs using the provided management functions.

Can I update an existing validation command without clearing the whole workflow?

Yes, the validation command registration supports upsert behavior, meaning you can create new or update existing named validation commands without clearing or rebuilding the entire validation workflow configuration.

What is the best way to manage code quality gates during integration?

The best way to manage code quality gates is to register shell commands as named validation steps, then apply them in CI-style workflows to run and monitor checks like lint, tests, and typechecks during integration.

How do I list and clear registered validation tasks across a codebase?

You can list and clear registered validation tasks across a codebase using the provided management functions, which allow you to view all configured validation commands and remove specific checks when they are no longer needed.

Does this validation tool track run results and fetch details for CI monitoring?

Yes, the validation tool tracks run results using a run result schema and provides functions to fetch run details. This allows you to monitor validation outcomes and verify code quality gates within your CI workflows.