create-inspection

What problem does it solve?

This Skill eliminates the guesswork and rushed, poorly evaluated fixes that come from not fully understanding a problem before acting, saving development time and reducing the risk of introducing new issues.

Core Features & Use Cases

• Evidence-Based Root Cause Diagnosis: Investigates code, tests, and logs to identify the actual source of a problem, not just its symptoms, with mandatory file:line citations for all claims.
• Multi-Option Fix Planning: Generates at least 2 distinct fix approaches with clear tradeoffs, effort estimates, and risk assessments for each, so you can pick the best fit for your context.
• Use Case: Use this before implementing any non-trivial fix, like resolving a flaky E2E test, an auth token race condition, or a performance regression, to avoid wasted effort on suboptimal solutions.

Quick Start

Use the create-inspection skill to investigate the flaky E2E login test failure and generate a structured fix path document saved to your project's docs/inspections directory.