Verify changes

Skill 26zl/universal-agent-skills/skills/verify-changes

Verify code or configuration changes with focused tests, static checks, and diff inspection before reporting completion. Use after implementing or modifying a repository; do not use for read-only explanations or when no files changed.From its SKILL.md

Install

npx -y skills add 26zl/universal-agent-skills --skill verify-changes

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

2 things to look at

17 days oldThe repository was created 17 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
1 stars1 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.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.7 KB, 278 tokens by cl100k_base, as published. Nobody here has run it

Verify Changes

Verify the actual change at the narrowest useful scope, then expand checks in proportion to risk.

Workflow

Inspect the final diff and list the behaviors that changed.
Identify the repository's documented validation commands before inventing new ones.
Run the smallest focused test that exercises each changed behavior.
Run the relevant formatter, linter, type checker, build, or broader test suite when the change can affect adjacent code.
Inspect generated files and user-visible output when automated assertions cannot cover layout or behavior.
Re-read the diff for accidental edits, debug output, secrets, stale comments, and missing tests.
Report which checks ran, their outcomes, and any check that could not run.

Rules

Do not claim success without fresh evidence from the current working tree.
Do not hide failing checks because they appear unrelated. Distinguish pre-existing failures only when evidence supports that conclusion.
Do not broaden the change merely to make unrelated checks pass.
Never expose credentials or sensitive output in logs or the final report.
Treat skipped checks as residual risk, not as passing checks.

Completion evidence

Provide a concise summary containing:

focused checks and their results;
broader checks and their results, when applicable;
manual inspection performed, when applicable;
remaining limitations or unverified behavior.

What ships with it: 1 file

191 B alongside SKILL.md

agents/

openai.yaml191 B