verified-change

Proves code changes merge-ready locally via test-first mutation checking and a verification gate.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/shawn-sandy/agentics-kit --skill verified-change-shawn-sandy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verified-change
Source: https://github.com/shawn-sandy/agentics-kit/tree/main/kit/plugins/code-testing-agent/skills/verified-change
Command: npx skills add https://github.com/shawn-sandy/agentics-kit --skill verified-change-shawn-sandy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? When hosted CI is unavailable or billing-blocked, red checks prove nothing and green never arrives, so merge readiness cannot be established remotely. This Skill proves a change is merge-ready entirely on the local machine by writing the test first, deliberately breaking the implementation to confirm the test can fail, then looping against a local verification gate until it passes. ## Core Features & Use Cases - Test-first with mutation checking: Writes the assertion before the change, then intentionally breaks the implementation to confirm the test actually goes red, using a catalogue of mutations by change type and a safe break-and-restore protocol with trap-based recovery. - Local merge gate: Installs and runs scripts/verify.sh, an auto-detecting gate that runs typecheck, lint, unit, and e2e stages, reporting explicit SKIP results for unconfigured tooling instead of silent passes. - Auditable VERIFICATION record: Emits a written record of every command actually run, the mutation applied with its observed failure output, and evidence paths, ready to paste into a PR body. - Use Case: You changed a guard clause in working code and CI is down. The Skill writes a boundary test, inverts the condition to watch the test fail, restores the file with byte-level cmp proof, implements the fix, loops on the gate, and hands you a VERIFICATION section for the PR. ## Quick Start Ask the agent to prove your current code change is merge-ready locally using the verified-change workflow before opening the pull request.

Frequently Asked Questions about verified-change

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

FAQPage Schema
How do I prove a code change is merge-ready without CI?▼

Run a local merge gate that executes typecheck, lint, unit, and e2e stages on your machine. Write the regression test first, mutation-check it by deliberately breaking the implementation, then loop on the gate until it passes and record every command in a VERIFICATION section.

What is mutation testing for a newly written test?▼

Mutation checking deliberately breaks the implementation, such as inverting a condition or shifting a boundary, to confirm the new test goes red. A test that stays green through the mutation proves nothing and must be rewritten before proceeding.

When should I use verified-change instead of a TDD loop?▼

Use verified-change when the code already works and red must be manufactured through mutation. For brand-new features where the code does not exist yet, use a TDD loop instead, since red is free and needs no mutation step.

Why use cmp instead of git diff to verify a file restore?▼

git diff --quiet ignores untracked files entirely, so it reports a clean tree over a file the change created that is still mutated. cmp -s compares bytes on disk and works whether the file is tracked, untracked, or ignored.

What happens if the verification gate keeps failing?▼

The loop stops after eight attempts and does not report success. It reports the failing assertion quoted from the gate output, the last diff attempted, and what has been ruled out so the next person does not retry it.

Is it safe to run the verify gate in any repository?▼

No. The gate executes whatever tooling the target repo declares, so running it in an unread repo is arbitrary code execution. Only run it in repositories you already trust.