verificationlisted

# Verification > **Note:** The bash examples below are reference snippets. If you enable > `disableSkillShellExecution` in Claude Code settings (v2.1.101+), any inline > shell execution from skills is blocked. These fenced examples are safe to read; > copy-paste them into your terminal to run. ## Beyond Unit Tests Unit tests verify code logic. Verification confirms the feature actually works in its real environment. Both are necessary. Neither alone is sufficient. The /verify command runs automated checks, but domain-specific verification often requires manual steps or specialized tooling. ## Closing the Feedback Loop Every change needs a feedback loop: make a change, verify it worked, then move on. The loop must be closed BEFORE committing. Bad workflow: change code -> commit -> move to next task -> discover it's broken Good workflow: change code -> verify -> commit -> move to next task ## Web Application Verification After changing UI or API behavior: 1. Start the dev server 2. Navigate to the affected page/endpoint 3. Test the happy path manually 4. Test at least one error path 5. Check browser console for errors/warnings 6. Verify responsive behavior if UI changed For API changes: ```bash # Test the endpoint directly curl -X POST http://localhost:3000/api/resource \ -H "Content-Type: application/json" \ -d '{"field": "value"}' # Check response status and body ``` ## API Verification Test beyond the happy path: - Valid request with all fields - Valid re