verify-change
Selects and executes the most targeted verification steps to confirm code changes, ensuring proven correctness.
Install
mkdir -p .claude/skills/verify-change && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18458" && unzip -o skill.zip -d .claude/skills/verify-change && rm skill.zipInstalls to .claude/skills/verify-change
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when behavior changed and you need to choose the smallest relevant verification first, then report evidence clearlyKey capabilities
- →Select the most relevant verification path for a change
- →Run repo-local checks first
- →Escalate verification only if needed
- →Report executed evidence clearly
- →Report remaining verification not run
- →Identify the smallest valid proof
How it works
The skill selects and runs the most relevant verification path for a change, prioritizing repo-local checks, and then reports the executed evidence and any remaining unverified aspects.
Inputs & outputs
When to use verify-change
- →Verifying a bug fix
- →Confirming behavior changes after a refactor
- →Providing proof of fix before PR merge
About this skill
What I Do
I select and run the most relevant verification path for a change and separate executed evidence from recommendations.
When To Use Me
- after a bug fix
- after a behavior change
- before claiming success
- when review needs direct verification evidence
Read Alongside
docs/ai/capabilities/verify-change/CAPABILITY.mddocs/ai/capabilities/verify-change/checklist.mddocs/ai/capabilities/verify-change/gotchas.mddocs/ai/capabilities/verify-change/examples.md
Project Commands
- Main verification command:
composer test - Main build command:
none (PHP tooling/docs kit; no compiled build step) - Main test command:
composer test (composer test:fast for parallel) - Preferred narrow-first pattern:
start with the narrowest repo-local check and escalate only if needed
Output
- selected command or flow
- why it is the smallest valid proof
- commands run
- results
- remaining verification not run
Gotchas
- do not claim success without running at least one direct check
- do not report a build success as proof of behavior correctness unless the project says otherwise
When not to use it
- →When behavior has not changed
- →When there is no need for direct verification evidence
Limitations
- →The skill does not claim success without running at least one direct check
- →The skill does not report a build success as proof of behavior correctness
- →The skill prioritizes repo-local checks
How it compares
This skill provides a structured and prioritized approach to verifying code changes, focusing on the smallest valid proof, unlike a general or ad-hoc testing process.
Compared to similar skills
verify-change side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| verify-change (this skill) | 0 | 23d | No flags | Intermediate |
| python-testing-patterns | 77 | 2mo | Review | Intermediate |
| dependency-upgrade | 26 | 4mo | Review | Intermediate |
| test-cases | 57 | 6mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by UtmostCreator
View all by UtmostCreator →You might also like
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
test-cases
cexll
This skill should be used when generating comprehensive test cases from PRD documents or user requirements. Triggers when users request test case generation, QA planning, test scenario creation, or need structured test documentation. Produces detailed test cases covering functional, edge case, error handling, and state transition scenarios.
reviewing-code
CaptainCrouton89
Systematically evaluate code changes for security, correctness, performance, and spec alignment. Use when reviewing PRs, assessing code quality, or verifying implementation against requirements.
wcag-audit-patterns
wshobson
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.
code-coverage-with-gcov
gadievron
Add gcov code coverage instrumentation to C/C++ projects