validation

Register and execute named validation commands for CI-style checks.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/Darsh20009/genmz-shop --skill validation-darsh20009
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validation
Source: https://github.com/Darsh20009/genmz-shop/tree/main/.local/skills/validation
Command: npx skills add https://github.com/Darsh20009/genmz-shop --skill validation-darsh20009

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the setup and execution of CI-style validation steps by registering named commands that can be triggered and monitored to verify code quality.

Core Features & Use Cases

  • Create or update a named validation command via setValidationCommand(name, command)
  • Remove a previously registered validation command via clearValidationCommand(name)
  • List all registered validation commands via getValidationCommands()
  • Execute one or more validation commands using startValidationRun(commandIds)
  • Stop a running validation run via stopValidationRun(runId, graceful?)
  • Inspect results with getValidationRun(runId) and getValidationRuns()
  • Follow conventional names and commands for common stacks

Quick Start

Register a lint command with npm run lint and run it to validate your code quality.

Frequently Asked Questions about validation

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

FAQPage Schema
How do I set up CI-style validation checks for my codebase?

CI-style validation checks are configured by registering named commands via setValidationCommand, then executing them in batches with startValidationRun to enforce quality gates like lint and tests across your project.

Can I stop a running validation run gracefully if a command takes too long?

Yes, you can gracefully stop a running validation run by calling stopValidationRun with the specific runId and passing the graceful flag to halt execution and inspect partial results.

How do I list all registered lint and test commands before running them?

You can list all registered validation commands by calling getValidationCommands, which retrieves every named shell command mapping defined for your project's quality checks.

Does this validation tool work across different programming languages and stacks?

Yes, the validation tool applies to codebases of varying sizes and languages, supporting conventional command mappings for common stacks to run lint, tests, and type checks.

What's the best way to track the status of multiple validation runs?

Track validation runs by using getValidationRun with a specific runId for individual status, or getValidationRuns to inspect results across all executed quality check batches.