validation

Register shell commands as named validation steps with run lifecycle management.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/scikrikci/skills --skill validation-scikrikci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validation
Source: https://github.com/scikrikci/skills/tree/main/skills/validation
Command: npx skills add https://github.com/scikrikci/skills --skill validation-scikrikci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Register shell commands as named validation steps (like CI checks) that can be triggered and monitored to verify code quality.

Core Features & Use Cases

  • Create or update named validation commands (e.g., lint, test, typecheck) that can be triggered on demand.
  • Start and monitor validation runs, aggregating statuses and logs for quick insight.
  • Stop or modify ongoing validation runs to adapt to evolving CI requirements.

Quick Start

Register a new validation command named lint with the shell command 'npm run lint'.

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 register shell commands as named validation steps by defining them with upsert semantics, allowing you to create or update checks like lint, test, and typecheck for CI-like workflows.

What is the best way to manage linting, testing, and type-checking commands on demand?

The best way to manage linting, testing, and type-checking is to register them as named validation commands that can be triggered, monitored, and stopped on demand to verify code quality.

Can I modify or stop ongoing validation runs to adapt to changing CI requirements?

Yes, you can stop or modify ongoing validation runs to adapt to evolving CI requirements, using the provided run lifecycle and stop capabilities to manage active checks.

How do I monitor validation runs and aggregate statuses for shell commands?

You monitor validation runs by starting them and aggregating statuses and logs, which returns structured results for each registered shell command to provide quick insight into code quality.

Does registering validation commands support updating existing checks without duplication?

Yes, registering validation commands supports upsert semantics, meaning you can create new checks or update existing named validation steps without creating duplicates.

What limitations should I consider when using shell commands for CI-like validation checks?

Consider that validation checks rely on shell commands executed within its lifecycle, meaning complex CI pipeline orchestrations may require external coordination beyond simple named validation steps.