validate

Runs read-only targeted tests and acceptance checks to report pass/fail or ship/no-ship verdicts on code changes.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill validate-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/pnewsam/skills/tree/main/archive/analysis-validation-evicted/validate
Command: npx skills add https://github.com/pnewsam/skills --skill validate-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? It answers whether recent code changes or a completed feature are actually safe to ship, without modifying any code, by mapping changes to the tests that cover them and verifying acceptance criteria against real evidence. ## Core Features & Use Cases - Changes mode: Spot-checks recent or uncommitted changes by diffing the relevant range, mapping changed source areas to the tests that exercise them, and running only those tests plus lint/typecheck. - Feature mode: Runs a comprehensive ship/no-ship pass on a completed feature, verifying each acceptance criterion with evidence and writing a validation report with a clear SHIP or NO-SHIP verdict. - Visual regression support: Compares before/after screenshots with a dependency-free pixel-diff helper for deterministic UI changes. - Use Case: Before opening a PR for a finished feature, run a feature-level validation pass that runs proportionate targeted and regression tests, confirms every acceptance criterion, and produces a validation report linked from the feature plan. ## Quick Start Use the validate skill to check my uncommitted changes against the relevant tests and report what passed, what failed, and what remains uncovered.

Frequently Asked Questions about validate

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

FAQPage Schema
How do I validate code changes before committing?▼

Run a changes-mode validation pass that diffs the relevant range, maps changed source areas to the tests that exercise them, and runs only those tests plus lint and typecheck. It reports pass/fail results and coverage gaps without modifying any code.

How to run a ship/no-ship check before opening a PR?▼

Use feature-mode validation: read the feature plan, run proportionate targeted and regression tests for the feature's blast radius, and verify each acceptance criterion against evidence. The result is a validation report with a clear SHIP or NO-SHIP verdict.

Can validation fix the test failures it finds?▼

No, validation is strictly read-only and never edits source or test files, installs packages, commits, or opens PRs. Surfaced defects are handed back as findings for a separate execution or fix step, after which you re-validate.

Does it run the entire test suite every time?▼

No, it runs proportionate checks: only the tests mapped to what changed, plus cheap lint and typecheck. If no tests cover a changed area, it runs smoke tests and flags the coverage gap rather than running everything blindly.

How do I compare screenshots for visual regression testing?▼

Use the bundled shot_diff.mjs helper with before and after screenshots captured on the same viewport with animations disabled. Identical screenshots exit 0; real differences exit 1, and the JSON report can be logged in the validation report.

What happens when an acceptance criterion cannot be verified?▼

An unverifiable criterion is treated as a no-ship, regardless of whether its checkbox is marked. Validation only certifies criteria confirmed with concrete evidence and never marks plan items complete beyond writing the report.