slack5-1770606136/.claude/commands/verify.md

description	argument-hint	allowed-tools
Verify completed work meets acceptance criteria and quality standards	<feature or task description to verify>	Task, Read, Write, Edit, Glob, Grep, Bash

Verify this work: $ARGUMENTS

Instructions

1. Understand What Was Done

Read recent commits and changed files:

git log --oneline -5
git diff HEAD~1 --stat

2. Check Acceptance Criteria

For each requirement:

• Implemented correctly?
• Tests pass?
• Edge cases handled?
• Error handling appropriate?

3. Run Quality Checks

go vet ./...
go test ./...
golangci-lint run ./... 2>/dev/null || true

4. Functional Verification

• Read the code path for the feature
• Verify inputs are validated
• Verify errors propagate correctly
• Check that the happy path works logically

5. Integration Check

• Does it work with existing code?
• Are there breaking changes?
• Are dependencies updated?

6. Report

## Verification Report: [Feature]

### Criteria
| Requirement | Status | Evidence |
|-------------|--------|----------|
| [requirement] | PASS/FAIL | [file:line or test name] |

### Quality
- Tests: PASS/FAIL (N tests)
- Lint: PASS/FAIL
- Vet: PASS/FAIL

### Issues Found
[Any problems discovered]

### Verdict: VERIFIED / NEEDS_WORK

Rules

• VERIFY with evidence, not assumptions
• RUN tests, don't just read them
• CHECK edge cases explicitly
• REPORT honestly - don't pass work that isn't ready