fix-verification

✅ Fix Verification Skill

Philosophy: A bug isn't fixed until it's verified. Twice.

When to Use

Use this skill when:

• You've implemented a bug fix
• Someone else's fix needs verification
• Deploying a fix to production
• Bug was high-impact and needs thorough verification
• Previous fixes for this bug have failed

Do NOT use this skill when:

• Just exploring code (no fix yet)
• Bug is trivial (e.g., typo fix)
• Running standard CI (automated verification)

---

Prerequisites

Before starting:

• Fix has been implemented
• You know the expected behavior
• You can reproduce the original bug (or have a failing test)
• You have access to test environment

---

Process

Phase 1: DIRECT VERIFICATION 🎯

Goal: Confirm the fix addresses the exact reported issue.

Steps:

1. Recreate the Original Bug Scenario

   Exact steps that caused the bug:
   1. [step 1]
   2. [step 2]
   3. [step 3]
   
   Expected result: [what should happen]
   Previous result: [what was happening - the bug]
   

2. Execute Test with Fix Applied

   • Follow exact same steps
   • Document actual result
   • Compare to expected

3. Verify the FIX, Not Just Absence of Error

   ❌ "It doesn't crash anymore" (incomplete)
   ✅ "It returns the expected user object with correct fields" (complete)
   

4. Test Multiple Times

   • Run at least 3 times
   • Note any inconsistency

Verification Checklist:

• Original bug scenario no longer produces error
• Expected behavior now occurs
• Result is consistent across multiple runs
• All variations of bug scenario work

---

Phase 2: EDGE CASE VERIFICATION 🔲

Goal: Ensure fix works for edge cases and variations.

Steps:

1. Identify Edge Cases

   edge_cases:
     boundary_values:
       - Empty input
       - Maximum length input
       - Minimum valid input
       - Just over limit
       - Just under limit
     
     special_inputs:
       - Null/undefined
       - Special characters
       - Unicode/emoji
       - Numbers as strings
       - Whitespace only
     
     state_variations:
       - First time user
       - Returning user
       - Admin user
       - Concurrent users
       - High load