verify

/verify - Pre-PR Verification Loop

Run all quality checks to ensure code is ready for PR submission.

Usage

/verify           # Run all 5 phases
/verify --quick   # Skip coverage check (faster)
/verify --fix     # Auto-fix formatting issues before check

Verification Phases

Execute each phase sequentially. If a blocking phase fails, stop and fix before continuing.

---

Phase 1: Sanity Check (Build)

Verify the CLI loads without errors:

node cli.js --version

Result	Meaning
Version displayed	PASS
Error thrown	FAIL (blocking)

---

Phase 2: Format Check (Lint)

Check code formatting with Prettier:

npx prettier --check "**/*.{js,cjs,mjs,json,md}" --ignore-path .gitignore

If issues found (--fix mode):

npx prettier --write "**/*.{js,cjs,mjs,json,md}" --ignore-path .gitignore

Result	Meaning
All files formatted	PASS
Files need formatting	WARN (non-blocking, fixable)

---

Phase 3: Test Suite

Run all tests with coverage:

npm run test:coverage

Coverage Requirements (from .claude/rules/testing.md):

Code Type	Minimum
General business logic	80%
Financial/Auth/Security	100%

Result	Meaning
Tests pass, coverage >= 80%	PASS
Tests pass, coverage < 80%	FAIL (blocking)
Tests fail	FAIL (blocking)

For --quick mode, run without coverage:

npm test

---

Phase 4: Security Scan

Scan for hardcoded secrets and debugging statements:

4.1 Check for console.log in production code:

grep -rn "console\.log\|console\.debug\|console\.info" --include="*.js" --include="*.cjs" --exclude-dir=node_modules --exclude-dir=tests --exclude-dir=coverage lib/ cli.js 2>/dev/null || echo "No console logs found"

4.2 Check for hardcoded secrets:

grep -rn "sk-[a-zA-Z0-9]\{20,\}\|ghp_[a-zA-Z0-9]\{36\}\|AKIA[A-Z0-9]\{16\}" --include="*.js" --include="*.cjs" --exclude-dir=node_modules lib/ cli.js 2>/dev/null || echo "No secrets found"