Change verification

Skill funky-eyes/best-copilot/skills/change-verification

Use after code or configuration changes to prove the changed behavior with minimal sufficient commands, HTTP/browser checks, or static evidence. DO NOT USE FOR: purely speculative review without a concrete change.From its SKILL.md

Install

npx -y skills add funky-eyes/best-copilot --skill change-verification

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.0 KB, as published. Nobody here has run it

Change Verification

Choose Evidence

Unit or integration tests for behavior changes.
Build/typecheck/lint for compile-time or static confidence.
HTTP or CLI commands for API/tool behavior.
Browser evidence for visible UI behavior.
Schema/frontmatter/residual scans for documentation, agent, skill, or plugin changes.

Minimum Report

## Verification
- command:
- result:
- evidence:
- coverage:
- gaps:

Rules

Do not claim “passed” without a command or concrete static check.
If a command cannot run, explain why and provide the strongest alternative evidence.
For public contract, auth, data, dependency, CI, or runtime config changes, include blast radius summary.