skills.rest
dbc-oduffy
dbc-oduffyCOMMUNITY
Explore all skills by this author →
GitHub

validate

Runs CI checks locally via .github/scripts/run-all-checks.py to validate repository health before merging.

5|2|Updated Mar 20, 2026
Search Tags:#validation#github actions#pre-commit#merge readiness#repository health#python scripts#ci
One-click install
npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill validate-dbc-oduffy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/dbc-oduffy/coordinator-claude/tree/main/plugins/coordinator/skills/validate
Command: npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill validate-dbc-oduffy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken changes from reaching the remote pipeline by running the repository’s full CI validation locally and surfacing failures early.

Core Features & Use Cases

  • Local CI execution: Runs .github/scripts/run-all-checks.py to perform all available validation checks in one pass.
  • Convention-based script discovery: Discovers and executes validate-*.py and check-*.py scripts under .github/scripts/ to cover repo-specific guardrails.
  • Pre-merge safety gate: Helps you confirm “All PASS” before committing, merging, or completing work, especially after modifying CI-related files or plugin manifests.

Quick Start

Run the validator by executing python .github/scripts/run-all-checks.py in your repository so you can review the full pass/fail output before proceeding.

Frequently Asked Questions about validate

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

FAQPage Schema
How do I run CI checks locally before merging to main?▼

Run local CI checks before merging by executing `python .github/scripts/run-all-checks.py` in your repository. This script performs all available validation checks in one pass, surfacing any failures early so you can confirm everything passes before committing or completing your work.

How does convention-based script discovery work for repository validation?▼

Convention-based script discovery for repository validation works by automatically finding and executing any files matching the `validate-*.py` and `check-*.py` naming patterns located under the `.github/scripts/` directory. This mechanism covers repo-specific guardrails during the local CI run.

When do I need to run local pre-commit validation scripts?▼

You need to run local pre-commit validation when preparing to commit, merge to main, or complete your workday, especially after editing CI scripts or configuration files. This pre-merge safety gate confirms all checks pass before broken changes reach the remote pipeline.

Does this local CI execution require any external dependencies?▼

No external dependencies are required to run this local CI execution. The validator operates by running the Python script located at `.github/scripts/run-all-checks.py` and relies entirely on your existing repository scripts for merge readiness checks.

What is the best way to prevent broken changes from reaching the remote pipeline?▼

The best way to prevent broken changes from reaching the remote pipeline is running the repository's full CI validation locally. By executing `run-all-checks.py` as a pre-merge safety gate, you can surface and fix failures early before committing code.

Related Skills

Explore More Software Engineering Skills→
oduffy-delphioduffy-delphi
5

validate

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

Community
Intermediate
omerakbenomerakben
1

git-workflow-deployment

Automate Git branching, CI/CD gates, and Vercel production deployments.

Community
Intermediate
dtsongdtsong
1

Git Merge Main

Merge the main branch into the current feature branch with conflict checks.

Community
Intermediate
tassosgomestassosgomes

java-production-readiness

Validate Java Spring Boot services against a pre-production readiness checklist.

Community
Advanced