verify-changes

name	verify-changes
description	Prove code works by running it, not just checking it exists. Verification through execution rather than inspection. Use after writing or modifying code to ensure it actually functions correctly.
when_to_use	After writing code, completing a feature, or fixing a bug. When the user says 'does this work?', 'test this', 'verify', or when /verify workflow is invoked. NOT for writing new code — for proving existing code works.
effort	medium

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