What problem does it solve? Intermittent Electron smoke-test failures in the Azure DevOps Flaky Smoke Tests pipeline (definition 700) are hard to investigate because iteration tasks use continueOnError, logs are shared across iterations, and artifacts can be overwritten or lost on cancellation. This Skill provides a systematic procedure to isolate the exact failed iteration, gather authoritative evidence, and trace the root cause. ## Core Features & Use Cases - Failed Iteration Discovery: Query the build timeline with Azure CLI to find iteration tasks with succeededWithIssues or failed results, and download exact per-task logs. - Artifact Correlation: Download platform log and crash artifacts, then correlate task timestamps with smoke-test-runner.log, mock-server requests, extension-host logs, screenshots, and Playwright traces. - Root Cause and Validation: Trace the introducing commit with git log and blame, then queue focused definition-700 validation runs with controlled iteration counts and platform selection. - Use Case: A chat smoke test fails intermittently on macOS. Use this Skill to pull the failed iteration's task log, confirm the mock server never received the scenario tag, identify the commit that introduced the dispatch race, and queue a six-iteration validation run to confirm the fix. ## Quick Start Ask the assistant to investigate the failed iterations of Azure DevOps build <BUILD_ID> from the Flaky Smoke Tests pipeline and identify the root cause.
