A specialized validation tool for .pre-commit-config.yaml files that enforces 23 distinct rules across structure, hooks, and best practices.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install pre-commit-config-validator
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install pre-commit-config-validator using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
The Pre-Commit Config Validator is a professional-grade tool designed to verify the integrity and compliance of .pre-commit-config.yaml files. It acts as a gatekeeper for your Git hooks, ensuring that every repository entry, hook definition, and local script is configured correctly before it enters production. By utilizing this skill from the Openclaw Skills library, developers can prevent broken CI pipelines and maintain a standardized environment for local development.
Beyond basic syntax checking, this validator implements deep inspection of hook schemas, including validation of staging values, language environments, and version pinning. It is an essential utility for teams aiming for high-quality codebase maintenance and automated governance of their development lifecycle through Openclaw Skills.
To start using this skill from Openclaw Skills, ensure you have Python 3 installed and the validator script available in your local path. Use the following commands to validate your configuration:
# Standard validation of the local config
python3 scripts/precommit_validator.py validate .pre-commit-config.yaml
# Run only best practices linting
python3 scripts/precommit_validator.py lint .pre-commit-config.yaml
# Use strict mode to fail on warnings
python3 scripts/precommit_validator.py validate .pre-commit-config.yaml --strict
The validator organizes its findings across five distinct rule categories, providing a clear taxonomy for diagnostics:
| Category | Rule Count | Focus Area |
|---|---|---|
| Structure (S) | 5 | YAML syntax, top-level keys, and required root keys. |
| Repository (R) | 6 | Repo URLs, rev pinning (SHA/tag), and hook list integrity. |
| Hooks (H) | 6 | Hook IDs, valid stages, argument lists, and additional dependencies. |
| Local (L) | 3 | Requirements for local repo types, including entry points and languages. |
| Best Practices (B) | 4 | Duplicate URLs, meta-hook usage, and semver pattern matching. |
Loading
A strategic tool for planning, estimating, and tracking large-scale codebase migrations from framework upgrades to language transitions.

A powerful utility to compare OpenAPI specifications and generate consumer-ready changelogs and migration guides.

A remote execution engine for managing Ollama task queues and automated code generation via SSH.

A comprehensive auditing tool designed to validate .dockerignore files for syntax errors, security leaks, and build context bloat.

A comprehensive diagnostic tool for identifying sync drift, diagnosing deployment failures, and auditing security for ArgoCD-managed applications.

A Python-powered CLI validator for devcontainer.json files that checks for structural errors, security risks, and configuration best practices.








































