run-validation

Execute validation steps from a Markdown file and compare outcomes.

1|Updated May 30, 2025
One-click install
npx skills add https://github.com/pkuppens/on_prem_rag --skill run-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-validation
Source: https://github.com/pkuppens/on_prem_rag/tree/main/.cursor/skills/run-validation
Command: npx skills add https://github.com/pkuppens/on_prem_rag --skill run-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of validating an implementation by executing predefined steps, tracking their success or failure, and facilitating diagnosis and correction of any issues encountered.

Core Features & Use Cases

  • Sequential Execution: Runs validation steps in a defined order, ensuring prerequisites are met.
  • Automated Verification: Compares actual outcomes against expected results for CLI commands, HTTP requests, UI checks, file operations, and log analysis.
  • Iterative Debugging: Guides the user through diagnosing failures, fixing implementation or validation issues, and re-running steps.
  • Use Case: After implementing a new feature, use this Skill to run through a comprehensive validation checklist to ensure all aspects of the feature work as intended before submitting a pull request.

Quick Start

Use the run-validation skill to execute the validation steps defined in the file 'validation.md'.

Frequently Asked Questions about run-validation

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

FAQPage Schema
How do I automate validation steps for a new feature implementation?

Automated verification runs predefined validation steps sequentially, comparing actual outcomes against expected results for CLI commands, HTTP requests, UI checks, file operations, and log analysis to ensure implementation correctness.

What is the best way to run a validation checklist before submitting a pull request?

Running a validation checklist sequentially executes steps defined in a Markdown file, tracking success or failure of CLI commands, HTTP requests, UI checks, file operations, and log analysis to ensure feature readiness before pull request submission.

Can I use Markdown to define automated testing and verification workflows?

Yes, Markdown files define automated verification workflows by specifying sequential validation steps that execute CLI commands, HTTP requests, UI checks, file operations, and log analysis, comparing actual outcomes against expected results.

How do I diagnose and fix failures when a validation step does not match expected results?

Diagnosing validation failures involves iterating on implementation or validation corrections, guiding users to identify mismatches between actual and expected outcomes, apply fixes, and re-run sequential steps to verify corrections.

Does sequential validation execution support HTTP requests and log analysis?

Sequential validation execution supports HTTP requests and log analysis alongside CLI commands, UI checks, and file operations, capturing and comparing actual outcomes against expected results for comprehensive implementation verification.