skills.rest
virahitvin8
virahitvin8COMMUNITY
Explore all skills by this author →
GitHub

verify-changes

Verify code changes by executing builds, tests, and runtime checks.

2|Updated May 30, 2026
Search Tags:#testing#quality assurance#bug fix#verification#code execution#runtime checks#build validation
One-click install
npx skills add https://github.com/virahitvin8/crafty-gis --skill verify-changes-virahitvin8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-changes
Source: https://github.com/virahitvin8/crafty-gis/tree/main/GIT_STAR/.agent/skills/verify-changes
Command: npx skills add https://github.com/virahitvin8/crafty-gis --skill verify-changes-virahitvin8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code that compiles or merely exists is often assumed to work, leading to undetected bugs reaching production. This Skill enforces verification through execution, requiring actual run evidence instead of inspection or assumption. ## Core Features & Use Cases - Execution-Based Verification Protocol: A four-step workflow that identifies what changed, selects the right verification method, executes it, and reports concrete evidence. - Change-Type Verification Matrix: Maps bug fixes, new features, refactors, API changes, UI changes, and config changes to appropriate verification commands. - Project-Type Checklists: Ready-made verification checklists for web applications, APIs/backends, and CLI scripts covering builds, tests, and runtime behavior. - Use Case: After fixing a bug in an API endpoint, run the verification protocol to reproduce the original failure scenario, confirm the fix via curl, and produce a structured evidence report. ## Quick Start Verify that the changes just made to the project actually work by running the build, tests, and relevant endpoints, then report the evidence.

Frequently Asked Questions about verify-changes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify that my code changes actually work?▼

Run the changed code and capture evidence: execute the build, run the test suite, and exercise the modified behavior at runtime. For APIs, call the endpoint with curl; for scripts, run them with real and edge-case inputs, then report the observed output.

How to test a bug fix before marking it done?▼

Reproduce the original bug scenario exactly as reported, then confirm the failure no longer occurs after the fix. Also run the existing test suite to ensure the fix did not break unrelated behavior.

What commands should I run to verify a Node.js project?▼

Run npm run build to confirm compilation, npm run test for the test suite, and npm run dev to check the server starts. For specific modules, use node -e with a require statement to confirm the file loads correctly.

Why is passing compilation not enough to confirm code works?▼

Compilation only proves syntax and types are valid, not that runtime behavior is correct. Logic errors, bad API responses, and broken edge cases only surface when the code actually executes with real inputs.

When should I skip running verification on code changes?▼

Never. Even trivial changes cause real bugs, so every modification should be verified through execution. The cost of running a build or test is far lower than shipping an unverified regression.

Related Skills

Explore More Software Engineering Skills→
Moonsong-LabsMoonsong-Labs
3

test-driven-development

Guide feature implementation by writing failing tests before code.

Official
Advanced
mattsp1290mattsp1290

ship

Coordinate review, fix, verify, commit, push, and pull request processes.

Community
Advanced
FastLEDFastLED
7.5k

test

Run unit and integration tests and report pass/fail results.

Official
Intermediate
Monjyu1101Monjyu1101
1

test-driven-development

Enforce a red-green-refactor workflow requiring failing tests before code implementation.

Community
Advanced