validate

Run local CI validation checks using Python scripts in .github/scripts/.

5|2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/oduffy-delphi/coordinator-claude --skill validate-oduffy-delphi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/oduffy-delphi/coordinator-claude/tree/main/plugins/coordinator/skills/validate
Command: npx skills add https://github.com/oduffy-delphi/coordinator-claude --skill validate-oduffy-delphi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams catch issues early by executing CI validation checks locally, preventing broken builds after commits or PRs.

Core Features & Use Cases

  • Local validation execution: Runs the repository's CI checks locally using the run-all-checks.py script to ensure consistent validation before remote pipelines.
  • Convention-based discovery: Automatically discovers and runs scripts named validate-.py and check-.py located in .github/scripts/ to cover common validation tasks.
  • Use Case: Before creating a PR, run the checks locally to verify that all validations pass and surface any failures early.

Quick Start

Run the local validation script to execute all CI checks before committing.

Frequently Asked Questions about validate

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

FAQPage Schema
How do I run GitHub Actions CI checks locally before committing?

Run GitHub Actions CI checks locally by executing the run-all-checks.py script, which automatically discovers and runs all validate-*.py and check-*.py validation scripts in .github/scripts/ to prevent broken builds before commits or pull requests.

What's the best way to validate Python scripts before creating a pull request?

The best way to validate Python scripts before a pull request is running local CI validation checks via run-all-checks.py, which surfaces failures early by executing all convention-based validate-*.py and check-*.py scripts found in .github/scripts/.

Do I need a Python runtime to run local CI validation checks?

Yes, you need a Python runtime to run local CI validation checks because the skill executes Python scripts located in .github/scripts/. Access to validate-*.py and check-*.py files is required to perform the validations.

How does convention-based script discovery work for local CI checks?

Convention-based script discovery works by automatically finding and executing files named validate-*.py and check-*.py within the .github/scripts/ directory, ensuring all common validation tasks run locally without manual configuration.

Why should I run CI checks locally instead of waiting for the remote pipeline?

Running CI checks locally catches issues early and prevents broken builds after commits or PRs. It ensures consistent validation by surfacing failures before triggering the remote GitHub Actions pipeline, saving development time.

Can I use local validation execution for repositories without GitHub Actions?

Local validation execution targets repositories relying on GitHub Actions and Python scripts. It requires access to .github/scripts/ containing validate-*.py and check-*.py scripts, so repositories without this structure are not supported.