validation

Register named shell-based validation commands and run CI-style checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Register named shell-based validation steps that run CI-style checks to verify code quality.

Core Features & Use Cases

  • Create, update, and delete named validation commands for lint, tests, and type checks.
  • Run and monitor validation runs across local development and CI workflows.
  • Retrieve, inspect, and audit all registered commands and their results.

Quick Start

Create a validation command with setValidationCommand and then startValidationRun to execute it.

Frequently Asked Questions about validation

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

FAQPage Schema
How do I run named CI-style validation checks for lint and tests?

To run CI-style validation checks, register named shell-based commands using setValidationCommand, then execute them via startValidationRun to verify code quality. This allows automated linting, testing, and type checking across local and CI workflows.

What is the best way to monitor automated validation runs in a CI workflow?

Monitoring validation runs involves retrieving execution status through getValidationRun and getValidationRuns after initiating checks with startValidationRun. This provides auditable results for CI-style code quality verification across local development and automated pipelines.

Can I update or remove registered shell commands for type checking?

Yes, you can update or remove registered shell commands for type checking by applying setValidationCommand to overwrite entries or clearValidationCommand to delete them. This manages the lifecycle of validation steps for software projects.

Does this validation approach work without external CI dependencies?

Yes, this validation approach works without external dependencies because it registers named shell-based steps internally. It independently satisfies functional requirements for linting, testing, and monitoring runs without requiring additional CI platform integrations.

How do I audit past validation runs and registered commands?

To audit past validation runs and registered commands, use getValidationCommands to inspect all defined steps and getValidationRuns to retrieve historical execution results. This provides a complete audit trail of code quality checks.