Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
vudovn avatar

Verify Changes

  • 19 installs
  • 8.1k repo stars
  • Updated August 4, 2026
  • vudovn/ag-kit

Helps with ai & agent building tasks.

About

verify-changes is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • verify-changes
  • AI & Agent Building
  • AI-coding skill

Verify Changes by the numbers

  • 19 all-time installs (skills.sh)
  • +2 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #10,587 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/vudovn/ag-kit --skill verify-changes

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs19
repo stars8.1k
Last updatedAugust 4, 2026
Repositoryvudovn/ag-kit

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

Verify Changes — Prove Code Works

"Code that exists" ≠ "Code that works." This skill ensures changes are verified through execution.

Core Principle

❌ Verification by inspection:  "I can see the function exists, it should work"
❌ Verification by assumption:  "The types check out, so it's correct"
✅ Verification by execution:   "I ran it, here's the output, it works because [evidence]"

---

Verification Protocol

Step 1: Identify What Changed

- Which files were modified?
- What behavior should be different now?
- What was the original bug/requirement?

Step 2: Determine Verification Method

Change TypeVerification Method
Bug fixReproduce the original bug scenario → confirm it no longer occurs
New featureRun the feature → confirm expected output
RefactorRun existing tests → confirm nothing broke
API changeCall the endpoint → confirm response shape
UI changeRender the component → confirm visual output
Config changeLoad the config → confirm values applied
Build/infraRun build command → confirm success

Step 3: Execute Verification

# For Node.js projects
npm run build          # Does it compile?
npm run test           # Do tests pass?
npm run dev            # Does it start?

# For specific files
node -e "require('./path/to/module'); console.log('✅ Loads correctly')"

# For API endpoints
curl http://localhost:3000/api/endpoint

# For scripts
python script.py --test

Step 4: Report Evidence

## Verification Report

### What was changed
- [File list and summary]

### How it was verified
- [Exact commands run]

### Evidence
- Build: ✅ Compiled without errors
- Tests: ✅ 42/42 passing
- Runtime: ✅ Server starts, endpoint returns expected JSON
- Edge case: ✅ Empty input handled correctly

### Not yet verified
- [Anything that couldn't be tested automatically]

---

Verification Checklist by Project Type

Web Application

  • [ ] npm run build — compiles without errors
  • [ ] npm run lint — no linting errors
  • [ ] npm run test — all tests pass
  • [ ] Dev server starts successfully
  • [ ] Changed pages render correctly
  • [ ] No console errors in browser

API / Backend

  • [ ] Server starts without errors
  • [ ] Changed endpoints respond correctly
  • [ ] Error cases return appropriate status codes
  • [ ] Database queries execute successfully

CLI / Script

  • [ ] Script runs without errors
  • [ ] Expected output matches actual output
  • [ ] Error handling works (bad input test)
  • [ ] Help/usage text is correct

---

Anti-Patterns

Anti-PatternWhy It's BadFix
"It should work"No evidenceRun it and show output
Only checking happy pathBugs hide in edge casesTest error paths too
Verifying only compilationCompiles ≠ correctTest runtime behavior
Skipping verification for "trivial" changesTrivial changes cause real bugsVerify everything

---

Integration with Other Skills

After UsingVerify With
frontend-design → UI changesRender in browser, check console
backend-specialist → API changescurl endpoints, check responses
database-design → Schema changesRun migrations, query data
testing-patterns → New testsRun test suite, check coverage

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.