What problem does it solve? Intermittent Electron smoke-test failures in the VS Code Flaky Smoke Tests pipeline (Azure DevOps definition 700) are hard to investigate because iteration tasks report succeededWithIssues, logs are shared across iterations, and artifacts can be overwritten or missing. This Skill provides a systematic procedure to locate the failed iteration, retrieve the right logs, and trace the root cause. ## Core Features & Use Cases - Failed Iteration Discovery: Query the build timeline with Azure CLI to find iteration tasks that failed or returned succeededWithIssues, and download their exact task logs. - Artifact Correlation: Download per-platform logs and crash-dump artifacts, then correlate the failed task's time range with the cumulative smoke-test-runner.log to isolate the failing interval. - Root Cause Tracing: Follow the gesture/dispatch/request/rendering chain, use git blame and git log to identify the introducing commit, and queue focused validation runs with custom iteration counts. - Use Case: A scheduled definition-700 run shows a red macOS iteration. Use this Skill to pull the timeline, download the task log and logs-macos-arm64 artifact, identify the racy commit, and queue a six-iteration validation run on your fix branch. ## Quick Start Diagnose the failed smoke-test iterations in Azure DevOps build 12345 from the Monaco project's flaky smoke tests pipeline.