Verify Changes

Quick Reference: Detect project type → Run typecheck → Run lint → Run tests → Run build → Score results → Report readiness.

After making code changes, this skill runs comprehensive verification to catch issues before commit.

When to Use

• After implementing a feature
• After fixing a bug
• Before creating a PR
• When unsure if changes broke something

Verification Strategy

1. Detect project type and available verification commands:

   • Check package.json scripts (test, lint, typecheck, build)
   • Check for pytest, cargo test, go test, forge test
   • Check for CI workflow files to understand what CI runs

2. Run verification in order of speed:

   • Type checking (fastest feedback)
   • Linting (catches style + some bugs)
   • Unit tests (catches logic errors)
   • Build (catches compilation errors)
   • E2E tests (if quick, or if specifically requested)

3. For web projects, optionally:

   • Start dev server
   • Test the UI with Playwright or manually
   • Verify the UX feels right

Package Manager Detection

Before running commands, detect the project's package manager:

# Detect package manager from lockfile
if [ -f "bun.lockb" ]; then
    PM="bun"
elif [ -f "pnpm-lock.yaml" ]; then
    PM="pnpm"
elif [ -f "yarn.lock" ]; then
    PM="yarn"
else
    PM="npm"
fi

Use $PM run <script> for all package.json script invocations.

Execution by Project Type

TypeScript/Node

# Use detected package manager (PM variable)
$PM run typecheck 2>&1 | head -50
$PM run lint 2>&1 | head -50
$PM run test 2>&1 | head -100
$PM run build 2>&1 | head -50

Python

ruff check . 2>&1 | head -50
mypy . 2>&1 | head -50
pytest -v 2>&1 | head -100

Rust

cargo check 2>&1 | head -50
cargo clippy 2>&1 | head -50
cargo test 2>&1 | head -100

Solidity/Foundry

forge build 2>&1 | head -50
forge test 2>&1 | head -100

Go

go vet ./... 2>&1 | head -50
go test ./... 2>&1 | head -100

Output Format

Return structured results with scoring:

Verification Results
====================
Score: 85/100

✓ Passed:
  - Type checking (tsc)
  - Linting (eslint)
  - Build (next build)

✗ Failed:
  - Unit tests (3 failures)

Critical (blocks merge):
  src/utils/auth.test.ts:45 - Expected token to be valid
  src/api/user.test.ts:23 - Missing mock for fetchUser
  src/api/user.test.ts:67 - Timeout exceeded

Warnings (should fix):
  [none]

Suggestions (nice to have):
  - Consider adding test for edge case in parseDate()

Summary: 3 critical, 0 warnings, 1 suggestion
Ready for commit: NO (fix critical issues first)

Severity Tiers

Scoring Rules

• Start at 100 points
• Deduct based on severity tier
• Minimum score: 0
• Ready for commit: Score ≥ 70 AND no critical issues