validate

Orchestrate validators on modified files and aggregate results into a pass/fail report.

22|3|Updated Jan 30, 2026

Search Tags:#parallel #orchestrator #validate #lint #validators #ci

Ready to run

npx skills add https://github.com/peteski22/claude-pragma --skill validate-peteski22

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/peteski22/claude-pragma/tree/main/skills/validators/validate
Command: npx skills add https://github.com/peteski22/claude-pragma --skill validate-peteski22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates validators to ensure consistent, automatic validation on recent code changes.

Core Features & Use Cases

Automatic validator orchestration: Runs applicable validators against changed files to guarantee code quality.
Parallel execution and aggregation: Spawns validator tasks in parallel and aggregates their results into a single, actionable report.
Use Case: In a PR workflow, it ensures all relevant linters and security checks pass before merging.

Quick Start

Run the validate skill to run all applicable validators on the latest changes and generate a consolidated report.

Frequently Asked Questions about validate

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

FAQPage Schema

How do I orchestrate multiple validators to run in parallel on recent code changes?▼

To orchestrate parallel validators on recent code changes, you can use a skill that detects modified files, selects the appropriate linters by language, spawns tasks concurrently, and aggregates the outputs into a single pass or fail report.

What is the best way to automatically run linters and security checks before a pull request merge?▼

The best way to automatically run linters before a PR merge is to orchestrate applicable validators against changed files, executing them in parallel to guarantee code quality and returning a clear pass or fail verdict for the commit.

How does validator orchestration aggregate results into a unified report for CI pipelines?▼

Validator orchestration aggregates results by spawning multiple validator tasks in parallel for modified files, collecting their outputs, and consolidating them into a single actionable report with a unified pass or fail verdict for CI workflows.

Can I run language-specific linters concurrently on only the modified files in my repository?▼

Yes, you can run language-specific linters concurrently on modified files by detecting the changed code, selecting the appropriate validators by language and task, and executing them in parallel to generate a consolidated validation report.

Does parallel validator execution support automatic detection of modified files?▼

Parallel validator execution supports automatic detection by identifying modified files in your repository, selecting the matching validators by language, and running them concurrently to ensure consistent validation on recent changes.

Why aggregate validator outputs instead of running linters individually for code checks?▼

Aggregating validator outputs instead of running linters individually consolidates multiple parallel task results into a single actionable report, providing a clear pass or fail verdict for commits and reducing manual output parsing.