name: Verification Skill description: Standardized QA and verification process for ensuring 0-defect delivery.

Verification Skill

This skill outlines the mandatory verification steps and quality checks that must be performed before reporting any task as complete.

1. Pre-Report Checklist (Verification Protocol)

Before saying "It is done" or "Please check", you MUST perform the following:

• Build Check: Does the code build? (Run npm run build or inspect for syntax errors).
• Integrity Check:
  • If git operations occurred, search for conflict markers (<<<<<<<, >>>>>>>) in ALL modified files.
  • Verify file ends and mismatched braces if large edits were made.
• Runtime Check: Have you executed the code?
  • If UI logic: Can you simulate the user flow?
  • If API logic: Have you verified the endpoint exists and works?
  • CRITICAL: If you modified an API route or Store method, you MUST verify the connection.
  • Firestore Sanitization: Have you ensured no undefined values are being sent to Firestore (use sanitizeData helper)?
• Error Check: Are there any console errors? (500, 404, etc.)

2. Data Consistency & QA Check Items

Before every delivery, verify there are no logical contradictions in the data:

• Section-Time Alignment: Is the task's scheduledStart actually within the boundaries of the assigned section?
• Time Range Validity: Is startTime < endTime? (Prevent negative durations).
• Status Integrity:
  • If status === 'done', is completedAt set?
  • If status === 'in_progress', is startedAt set?
  • If a task is not active, are startedAt and completedAt correctly managed?
• Sequential Integrity: Are order fields correctly assigned to prevent overlapping or missing gaps?

3. Acceptance Test Rules

Mandatory Checklist for Developers:

• Functional Verification: Does the feature solve the specific problem described?
• UI/UX Consistency: Does the design match the established aesthetic and responsiveness of the app?
• Data Integrity: Are all new fields sanitized? Are there logical contradictions in the saved data?
• Role-Based Access: If applicable, are Firestore rules updated and tested?

Standard Quality Gates

• Build Success: npm run build passes without errors.
• Linting: No critical ESLint warnings or errors in the modified files.
• Sanitization: Use sanitizeData helper for all Firestore writes.

4. QA Test Sheet (Reference)

When verifying features, refer to these standard test cases:

5. Failure Protocol

• If an error is found by the user that you could have caught: 2. Fix the error. 3. Determine prevention for the future.

6. Post-Merge/Conflict Protocol

If you have resolved a git conflict or performed a complex merge/rebase:

1. Search globally for <<<<<<<, =======, >>>>>>> to ensure no markers were missed.
2. Verify syntax of the entire file, specifically focusing on:
   • Closing braces } for functions/classes (often lost in merges).
   • Import statements (often duplicated).
3. Clean Build: Run a fresh build/type-check (npm run build or tsc --noEmit) to catch structural errors that incremental builds might miss.