verification

Verification Skill

Skill Metadata

• Name: verification
• Description: Structured multi-phase verification of implementations before deployment
• User Invocable: Yes (via /verify)

---

Overview

This skill provides a structured approach to verifying that implementations are complete, correct, and ready for deployment. It ensures no step is missed before considering work done. The discipline is stack-agnostic; the examples below use TypeScript / Node.js as a concrete illustration, but the same phases apply to any language or runtime.

---

Verification Checklist

1. Code Quality

Type Checking (TypeScript example)

# Backend service
npx tsc --noEmit -p apps/<service>/tsconfig.json

# Frontend app
cd apps/<frontend> && npx tsc --noEmit

For other typed languages, substitute the equivalent compiler invocation (e.g., go build ./... for Go, mypy . for Python with mypy, cargo check for Rust).

Linting

# Run lint across the workspace
npm run lint

# Or service-by-service
npm run lint --workspace=apps/<service>

2. Tests

Unit Tests

# Run all unit tests
npm test

# Check coverage
npm test -- --coverage

Integration Tests

# Run integration / end-to-end tests
npm run test:e2e

3. Functionality

Endpoint Verification

# Health check
curl http://localhost:<port>/health

# Test a specific endpoint
curl -X POST http://localhost:<port>/api/v1/<resource> \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"field": "value"}'

Database Verification

# Check pending migrations (adjust for your ORM / migration tool)
# Example using a generic migration CLI:
npx your-orm migrate status

# Verify the schema matches expectations
npx your-orm db pull --print

4. Security

Authentication Check

• Endpoints require authentication where appropriate
• Token validation works correctly
• Unauthorized requests return 401