Validate CI and app config files against upstream JSON schemas before merge
Use check-jsonschema when an agent needs to catch broken GitHub Actions, Renovate, Azure Pipelines, and other schema-backed config files before they hit CI. The agent picks the right schema hook, validates the changed files, and reports the exact key or structure that drifted from the contract.
npx skills add agentskillexchange/skills --skill validate-ci-and-app-config-files-against-upstream-json-schemas-before-merge
This skill uses check-jsonschema, the JSON Schema CLI and pre-commit hook maintained at python-jsonschema/check-jsonschema, to verify configuration files against official schemas before a branch is merged. It is a good fit when an agent is working in a repository full of operational config, not when the job is ordinary code linting. The useful trick here is that the tool already knows about common config families such as GitHub Actions workflows, Renovate, Azure Pipelines, Read the Docs, Dependabot, and other schema-backed files, so the agent can validate the real contract instead of just checking that the YAML parses.
What this skill actually does
Invoke this skill when the agent is editing CI or automation files, reviewing a pull request that touches infrastructure config, or building a pre-merge guardrail for repositories that depend on schema-driven config. In those moments, using the product normally by hand is too brittle: an agent should discover which files changed, run the matching hook or schema target, and turn the failures into a concrete fix list. That makes it meaningfully different from listing a generic validator. The job is not “use a CLI.” The job is “stop schema drift before it breaks automation.”
The scope boundary matters. This is not a general YAML linter, not a JSON Schema authoring toolkit, and not an SDK entry. It is a narrow validation skill for config that already has an upstream schema. Typical integrations include pipx install check-jsonschema, brew install check-jsonschema, pre-commit hooks, and CI steps that run on changed files only. Documentation lives at check-jsonschema.readthedocs.io, and the upstream repo publishes releases and packaged builds that agents can pin in repeatable workflows.