Update E2E Troubleshooting

Documenting E2E troubleshooting patterns requires capturing the symptom, root cause, solution, and discovery method in a consistent format. This Skill standardizes that process by generating properly formatted troubleshooting items with sequential numbering, enabling teams to build a reusable knowledge base across the Quick Troubleshooting Checklist.

When recording a resolved Playwright E2E test failure, include the symptom (what failed), root cause (why it failed), solution (how you fixed it), and discovery method (how you found the root cause). This Skill ensures each element is documented consistently so the pattern can be applied to similar failures across your test suite.

Extracting a reusable pattern involves identifying the generic conditions that triggered the failure, abstracting away test-specific details, and documenting the solution steps in a form other team members can recognize and apply. This Skill generates that generic pattern automatically and assigns it the next sequential number in your troubleshooting knowledge base.

Yes. This Skill is designed to standardize how new troubleshooting items are added to a Quick Troubleshooting Checklist, maintaining consistent formatting and sequential numbering. Each new resolved failure becomes a documented pattern teams can reference before investigating similar issues.

Standardizing how you document troubleshooting patterns—including symptom, root cause, solution, and discovery method—ensures knowledge persists in a structured, searchable form. This Skill enforces that standardization automatically, turning ad-hoc fixes into documented patterns that survive team transitions.