claude-plugins/plugins/workflow/commands/verify.md

description: End-to-end verification of implementation using subagent argument-hint: [scope] - Optional scope (e.g., "auth flow", "api endpoints")

Verify Implementation

Pre-computed Context

Changed Files: !git diff --name-only HEAD~5 2>/dev/null | head -20 || git diff --name-only --cached

Recent Commits: !git log --oneline -5

Package Scripts: !cat package.json 2>/dev/null | grep -A 20 '"scripts"' | head -25 || echo "No package.json"

Test Files: !find . -name "*.test.*" -o -name "*.spec.*" 2>/dev/null | head -10 || echo "No test files found"

---

Instructions

You are performing end-to-end verification of recent changes. This is a thorough check before committing or creating a PR.

Verification Checklist

1. Static Analysis

Run available linters and type checkers:

# TypeScript
npx tsc --noEmit 2>/dev/null || echo "No TypeScript"

# ESLint
npx eslint . --ext .ts,.tsx,.js,.jsx 2>/dev/null || echo "No ESLint"

# For Python
python -m mypy . 2>/dev/null || echo "No mypy"
ruff check . 2>/dev/null || echo "No ruff"

2. Unit Tests

Run tests for changed files:

# Jest
npx jest --passWithNoTests 2>/dev/null || echo "No Jest"

# Vitest
npx vitest run 2>/dev/null || echo "No Vitest"

# pytest
pytest 2>/dev/null || echo "No pytest"

3. Build Verification

Ensure the project builds:

npm run build 2>/dev/null || yarn build 2>/dev/null || echo "No build script"

4. Manual Code Review

For each changed file, verify:

• No hardcoded secrets or credentials
• Error handling is present where needed
• No obvious security vulnerabilities (SQL injection, XSS, etc.)
• Code follows existing patterns in the codebase

5. Integration Check

If the scope argument is provided, focus verification on that area:

• Read related files
• Trace the data flow
• Verify edge cases are handled

Report

After verification, provide a summary:

## Verification Report

### Passed
- [x] TypeScript compilation
- [x] Unit tests (X passed)
- [x] Build successful

### Issues Found
- [ ] Issue 1: description
- [ ] Issue 2: description

### Recommendations
- Suggestion 1
- Suggestion 2

---

Subagent Mode

For comprehensive verification, this command can spawn a verification subagent:

Use the Task tool with subagent_type="general-purpose" to:
1. Read all changed files
2. Run all available test suites
3. Check for common issues
4. Report findings

The subagent has access to Bash, Read, Grep, and Glob tools to perform thorough verification.