validation

Register and orchestrate named validation commands for CI-style code-quality checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Register a set of named validation commands (lint, test, typecheck, etc.) that can be triggered, monitored, and reported as CI-style gates to verify code quality.

Core Features & Use Cases

  • Define or update named validation commands via setValidationCommand(name, command).
  • Remove a validation command with clearValidationCommand(name).
  • Enumerate all commands using getValidationCommands() and monitor run statuses with startValidationRun(commandIds), stopValidationRun(runId, graceful?).
  • Retrieve detailed results using getValidationRun(runId) or list multiple runs with getValidationRuns().
  • Use cases: set up a quality gate for a project, evolve checks over time, and gate deployments based on validation outcomes.

Quick Start

Define a lint and a test command, then start a run to validate your project’s quality gates.

Frequently Asked Questions about validation

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

FAQPage Schema
How do I automate lint and typecheck validation commands for CI-style quality gates?

You can automate lint and typecheck validation by registering named commands via an API, then orchestrating and monitoring them as CI-style quality gates to verify code quality before deployment.

What is the best way to monitor the status of automated test runs and code-quality checks?

The best way to monitor automated test runs is to start a validation run for specific command IDs, then query the detailed results and observable logs to track whether the code-quality checks pass or fail.

Can I update or remove existing validation checks as my project's requirements evolve?

Yes, you can update existing validation checks using upsert behavior to redefine commands, or remove them entirely by clearing the validation command by its registered name when project requirements change.

Does this validation tool support enumerating all registered commands and retrieving historical run logs?

Yes, the validation tool supports enumerating all registered commands and retrieving historical run logs, allowing you to list multiple past runs and query detailed results for observable monitoring.

How do I stop a validation run that is currently executing a quality gate check?

You can stop a currently executing validation run by calling the stop API with the specific run ID, with an option to perform either a graceful or immediate termination of the quality gate check.