About jww-repository-validation
jww-repository-validation is a skill for choosing checks to validate repository changes. It guides developers to discover existing project instructions and run a proportionate set of checks, from documentation review to focused tests.
Key features
- 01Inspect repository guidance and automation
- 02Prefer documented validation commands
- 03Match checks to change scope and risk
- 04Use read-only checks before state-changing steps
- 05Classify and report check results
Use cases
- 01Choose checks for a code change
- 02Validate documentation or configuration edits
- 03Decide whether broader integration checks are warranted
- 04Report skipped checks and remaining risks
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/jww-repository-validationin Claude Code to confirm it loaded.
Bundled filesagents/openai.yaml
Details
From the project READMERepository Validation
This is the general-purpose fallback for deciding how to validate a change when nothing else has specified it. Repository instructions and documented validation commands take precedence over these defaults.
Proportionate means matching the checks' scope and cost to the blast radius of the change. Run the smallest sufficient set that covers the changed artifact and behavior, widening to integration or end-to-end checks as the change's reach grows.
Discover the Checks
- Read applicable
AGENTS.md,README, contributor guidance, and nearby automation before choosing commands. - Inspect changed file types and available configuration such as
.editorconfig, package manifests, CI workflows, task runners, and formatter or linter settings. - Prefer an existing documented check over inventing a new one.
Choose Proportionate Validation
- Documentation: review readability and run
git diff --check; run an available Markdown check when the repository uses one. - Source code: when edits are authorized, format only changed files. Run focused tests, static analysis, or builds that exercise the change. For read-only review, report formatting differences without changing files.
- Configuration, templates, and scripts: render, parse, or dry-run the affected artifact, and run a syntax check when applicable.
- Broad or risky changes: add the relevant integration or end-to-end check when available.
Start with read-only checks. Do not install dependencies, apply configuration, migrate data, publish artifacts, or otherwise change external state merely to validate unless the task authorizes those effects.
Once the required, relevant checks pass, proceed toward completion. Broaden or repeat validation only when further changes, failures, or unresolved concerns justify it.
Report Results
- Review failures against the changed behavior before declaring them regressions.
- Report each exact command or named check and classify its result as passed, change-related failure, pre-existing failure, environment blocker, or skipped.
- For skipped checks, state why they were unavailable or disproportionate and identify the remaining risk.