validation

Register and run named shell validation commands with per-command exit codes and logs.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/rezosnd/MINI-PROJECT- --skill validation-rezosnd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validation
Source: https://github.com/rezosnd/MINI-PROJECT-/tree/main/ML%20BACKEND%20DASHBOARD/.local/skills/validation
Command: npx skills add https://github.com/rezosnd/MINI-PROJECT- --skill validation-rezosnd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a repeatable way to register and execute named shell validation commands (lint, test, typecheck, format, etc.) and to monitor their execution so teams can quickly detect regressions, inspect failures, and access full logs for troubleshooting.

Core Features & Use Cases

  • Named Validation Commands: Create, update, and remove short identifiers mapped to shell commands for consistent quality gates across environments.
  • Run Management: Start, stop, and list validation runs that execute one or more registered commands and report per-command exit codes, durations, and log file paths.
  • Summaries & Debugging: Receive an LLM-generated run summary with log line citations to understand failures without reading full logs, and inspect per-command logs for root-cause analysis.
  • Use Case: On feature branches, register lint, test, and typecheck commands, run them before opening a pull request, and use the run summary to triage any issues before merging.

Quick Start

Register lint and test commands and start a validation run to get a summarized result with per-command statuses and links to the full logs.

Frequently Asked Questions about validation

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

FAQPage Schema
How do I run lint and test checks before opening a pull request?

A validation run executes registered shell commands like lint and test, reporting per-command exit codes, durations, and log file paths. You receive an LLM-generated run summary with log line citations to triage issues before merging.

What is pre-merge validation automation for code quality?

Pre-merge validation is the process of executing registered shell commands like lint, typecheck, and test to verify code quality and detect regressions. It reports per-command exit codes, durations, and log file paths along with an LLM-generated run summary.

How do I register and update named shell commands for CI validation?

You can create, update, and remove short identifiers mapped to shell commands to establish consistent quality gates across environments. These named validation commands are then executed together during a validation run across development and CI-like scenarios.

Can I get a summarized report of test and lint failures without reading full logs?

Yes, validation runs provide an LLM-generated run summary with log line citations to understand failures without reading full logs. You can also inspect per-command logs for root-cause analysis when triaging issues.

Does this validation tool work with existing CI-like automation scenarios?

Yes, it is designed for CI-like automation scenarios and applies to project repositories. You can start and stop validation runs that execute one or more registered commands and report the overall run status alongside per-command durations.

What are the limitations of running named shell commands for validation?

The tool requires you to manually register and map shell commands to short identifiers before running. It reports exit codes, durations, and log paths but relies on external shell commands for the actual lint, test, typecheck, and format execution logic.