debug-visual-regression

# Debug Visual Regression Automatically analyze visual regression failures when the user mentions them. This Skill helps identify the root cause of visual differences and suggests whether to accept or fix changes. ## When to Use This Skill Activate this Skill when the user: - Mentions "failing visual test" or "screenshot failure" - Asks "what's wrong with my visual tests?" - Says "the homepage screenshot is different" or similar - Wants to understand why a visual comparison failed - Asks to "debug", "analyze", or "investigate" visual changes - Mentions specific screenshot names that are failing ## How This Skill Works 1. **Automatically detect the mode** (local TDD or cloud) 2. **Fetch comparison details** using the screenshot name or comparison ID 3. **View the actual images** to perform visual analysis 4. **Provide detailed insights** on what changed and why 5. **Suggest next steps** (accept, reject, or fix) ## Instructions ### Step 1: Call the Unified MCP Tool Use `read_comparison_details` with the identifier: - Pass screenshot name (e.g., "homepage_desktop") for local mode - Pass comparison ID (e.g., "cmp_abc123") for cloud mode - The tool automatically detects which mode to use - Returns a response with `mode` field indicating local or cloud ### Step 2: Check the Mode in Response The response will contain a `mode` field: - **Local mode** (`mode: "local"`): Returns filesystem paths (`baselinePath`, `currentPath`, `diffPath`) - **Cloud mode** (`mode: "cloud"`): R...