verify-changes

name	verify-changes
description	"Code that exists" ≠ "Code that works." This skill ensures changes are verified through execution.

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 Type	Verification Method
Bug fix	Reproduce the original bug scenario → confirm it no longer occurs
New feature	Run the feature → confirm expected output
Refactor	Run existing tests → confirm nothing broke
API change	Call the endpoint → confirm response shape
UI change	Render the component → confirm visual output
Config change	Load the config → confirm values applied
Build/infra	Run build command → confirm success

Step 3: Execute Verification

# For Node.js projects
npm run build          
npm run            
npm run dev            


node -e 


curl http://localhost:3000/api/endpoint


python script.py --