Skip to content

Latest commit

 

History

History
45 lines (27 loc) · 1.93 KB

03-verification.md

File metadata and controls

45 lines (27 loc) · 1.93 KB

03. Verification Phase

Goal: Prove it works before asking for review.

3.1 Pre-Merge Checklist (Mandatory)

Before merging any branch to main, all checks must pass:

  1. Type Safety: tsc --noEmit --pretty (or lang equivalent)
  2. Production Build: npm run build
  3. Commit History: git log main..{branch} --oneline (clean history)

All three must exit with code 0. Build warnings are acceptable; errors are not.

Solo Mode: During rapid development, the minimum bar is: build passes. Type checks and lint are strongly recommended but not blocking for iterative work. Before any deploy to production, use the full Solo Verification Checklist.

3.2 Post-Merge Verification

After merging to main:

  1. Pull & Rebuild: Confirm no merge artifacts broke the build.
  2. Verify Integrations: Check critical paths (login, payments, core flows).

Solo Mode: No staging environment required. Localhost verification is sufficient during development. After deploying to production, do a 2-minute smoke test: load the app, test the happy path, check the console for errors.

3.3 Visual Verification

For any UI change:

  1. Localhost: Verify desktop and mobile viewports.
  2. Themes: Check light/dark mode if applicable.
  3. States: Verify loading, empty, and error states manually.
  4. Motion: Confirm animations differ from static designs (smooth transitions).

3.4 Performance Verification

For performance-sensitive changes:

  1. Bundle Size: Check impact on build output.
  2. Profiling: Verify render performance for frequent updates.
  3. Memory: Verify no leaks in hooks or event listeners.

Related: 02-Execution · 07-Testing · 08-Deployment · AI Verification Duties · Verification Checklist