[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-dotnet-ci-analysis":3,"mdc--hhlmud-key":36,"related-repo-dotnet-ci-analysis":1128,"related-org-dotnet-ci-analysis":1217},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":25,"repoUrl":26,"updatedAt":27,"license":28,"forks":29,"topics":30,"repo":31,"sourceUrl":34,"mdContent":35},"ci-analysis","analyze .NET CI build and test status","Analyze CI build and test status from Azure DevOps and Helix for dotnet repository PRs. Use when checking CI status, investigating failures, determining if a PR is ready to merge, or given URLs containing dev.azure.com or helix.dot.net. Also use when asked \"why is CI red\", \"test failures\", \"retry CI\", \"rerun tests\", \"is CI green\", \"build failed\", \"checks failing\", or \"flaky tests\". DO NOT USE FOR: investigating stale codeflow PRs or dependency update health, tracing whether a commit has flowed from one repo to another, reviewing code changes for correctness or style.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"dotnet",".NET (Microsoft)","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fdotnet.png",[12,16,19,22],{"name":13,"slug":14,"type":15},"Azure","azure","tag",{"name":17,"slug":18,"type":15},".NET","net",{"name":20,"slug":21,"type":15},"CI\u002FCD","ci-cd",{"name":23,"slug":24,"type":15},"Debugging","debugging",12,"https:\u002F\u002Fgithub.com\u002Fdotnet\u002Farcade-skills","2026-07-12T08:21:49.360882",null,18,[],{"repoUrl":26,"stars":25,"forks":29,"topics":32,"description":33},[],"Reuseable AI skills, plugins, agents for use in the dotnet product repos, such as dotnet\u002Fruntime","https:\u002F\u002Fgithub.com\u002Fdotnet\u002Farcade-skills\u002Ftree\u002FHEAD\u002Fplugins\u002Fdotnet-dnceng\u002Fskills\u002Fci-analysis","---\nname: ci-analysis\ndescription: >\n  Analyze CI build and test status from Azure DevOps and Helix for dotnet repository PRs.\n  Use when checking CI status, investigating failures, determining if a PR is ready to merge,\n  or given URLs containing dev.azure.com or helix.dot.net. Also use when asked \"why is CI red\",\n  \"test failures\", \"retry CI\", \"rerun tests\", \"is CI green\", \"build failed\", \"checks failing\",\n  or \"flaky tests\". DO NOT USE FOR: investigating stale codeflow PRs or dependency update health,\n  tracing whether a commit has flowed from one repo to another, reviewing code changes for\n  correctness or style.\n---\n\n# Azure DevOps and Helix CI Analysis\n\nAnalyze CI build status and test failures in Azure DevOps and Helix for dotnet repositories (runtime, sdk, aspnetcore, roslyn, and more).\n\n> 🚨 **NEVER** use `gh pr review --approve` or `--request-changes`. Only `--comment` is allowed. Approval and blocking are human-only actions.\n\n**Workflow**: Gather PR context (Step 0) → collect failure data → synthesize recommendations. The agent drives the investigation; tools provide the data.\n\n**Accessing services**: Start with MCP tools if available. Get repo-specific CI guidance early — it provides the investigation workflow, tool selection, failure patterns, and classification algorithm for that repo. The guidance evolves with the toolset, so it always reflects current capabilities.\n\nIf MCP tools aren't loaded, the Helix CLI tool provides the same capabilities via bash with progressive discovery.\n\nFor AzDO, multiple tool sets may exist for different organizations — match the org in the build URL to the correct tools (see [references\u002Fazdo-helix-reference.md](references\u002Fazdo-helix-reference.md#azure-devops-organizations)). If queries return null, check the org before trying other approaches. For complex investigations, track what you've tried in SQL to avoid repeating failed approaches.\n\n## When to Use This Skill\n\n- Checking CI status (\"is CI passing?\", \"why is CI red?\")\n- Investigating CI failures or determining merge readiness\n- Debugging Helix test issues or build errors\n- URLs containing `dev.azure.com`, `helix.dot.net`, or GitHub PR links with failing checks\n- Questions like \"retry CI\", \"rerun tests\", \"test failures\", \"checks failing\"\n- Investigating canceled or timed-out jobs for recoverable results\n\n**Not for**: GitHub Actions workflows, non-Helix repos, or build performance (use binlog analysis).\n\n> 💡 **Per-repo CI patterns differ significantly.** Get repo-specific guidance early — it tells you which tools to use, what log patterns to search for, and what gotchas to expect. This is the fastest path and prevents wasted calls.\n\n## Quick Start\n\n1. **Get repo-specific CI guidance** — investigation workflow, tool selection, search patterns, and failure classification for that repo\n2. **Find builds** for the PR or use a build ID directly\n3. **Follow the investigation order** from the guidance — it tells you what to check and in what sequence\n\nIf MCP tools aren't available, the Helix CLI tool provides the same capabilities via bash. A legacy PowerShell script is also available for environments that support it.\n\nFor full parameter reference and mode details, see [references\u002Fscript-modes.md](references\u002Fscript-modes.md).\n\n## Step 0: Gather Context (before running anything)\n\n1. **Read PR metadata** — title, description, author, labels, linked issues\n2. **Classify the PR type**:\n\n| PR Type | How to detect | Interpretation shift |\n|---------|--------------|---------------------|\n| **Code PR** | Human author, code changes | Failures likely relate to the changes |\n| **Flow\u002FCodeflow PR** | Author is `dotnet-maestro[bot]`, \"Update dependencies\" | Missing packages may be behavioral, not infrastructure |\n| **Backport** | Title mentions \"backport\", targets release branch | Check if test exists on target branch |\n| **Merge PR** | Merging between branches | Conflicts cause failures, not individual changes |\n| **Dependency update** | Bumps package versions, global.json | Build failures often trace to the dependency |\n\n3. **Check existing comments** — has someone already diagnosed failures or is a retry pending?\n4. **Note the changed files** — you'll use these for failure correlation\n\n## After Data Collection: Synthesize\n\n> 🚨 **Don't re-fetch data you already have.** Only make additional calls for deeper investigation (Helix log searches, binlog analysis, build progression).\n\n**Classify each failure.** Determine whether it's a build error, test failure, crash, timeout, or infrastructure issue. Exit codes, log patterns, and Helix work item state all contribute — the repo-specific CI guidance includes a classification algorithm with the patterns and recommended next steps for each category. Crashes (exit code -4, 139, 134) don't always mean tests failed — check for recoverable test results before concluding.\n\n**Cross-reference with known issues.** Check which failures are already matched by Build Analysis — green means all failures are accounted for, red means some are unmatched. For each unmatched failure, search for related known issues by error message, test name, or job type. The user needs a per-failure verdict, not two separate lists.\n\n**Correlate with PR changes.** If the same files appear in both the PR diff and the failure messages, the failure is likely PR-related. If not, check whether the same test fails on the target branch — that distinguishes pre-existing flakes from regressions.\n\n**Verify before claiming.** Don't call it \"infrastructure\" without a Build Analysis match or target-branch verification. Don't call it \"safe to retry\" unless ALL failures are accounted for.\n\n> 🚨 **Check build progression on multi-commit PRs.** If the PR has multiple commits, query AzDO for builds on `refs\u002Fpull\u002F{PR}\u002Fmerge` (sorted by queue time, top 10-20). Present a progression table showing which builds passed\u002Ffailed at which SHAs — this narrows failures to the commit that introduced them. See [references\u002Fbuild-progression-analysis.md](references\u002Fbuild-progression-analysis.md).\n\nFor interpreting error categories, crash recovery, and canceled jobs: [references\u002Ffailure-interpretation.md](references\u002Ffailure-interpretation.md)\n\nFor generating recommendations from `[CI_ANALYSIS_SUMMARY]` JSON: [references\u002Frecommendation-generation.md](references\u002Frecommendation-generation.md)\n\n## Presenting Results\n\n> 🚨 **Keep tables narrow — 4 short columns max (# | Job | Verdict | Issue).** Put error descriptions, work item lists, and evidence in **detail bullets below the table**, not in cells. Wide tables wrap and become unreadable in terminals.\n\n> 🚨 **Use markdown links** for PRs (`[#121195](url)`), builds (`[Build 1305302](url)`), and jobs (`[job name](azdo-job-url)`). The script output and MCP tools provide URLs — thread them through.\n\nLead with a 1-2 sentence verdict, then the summary table, then detail bullets (one per failure), then recommended actions. For the full format example: [references\u002Frecommendation-generation.md](references\u002Frecommendation-generation.md).\n\n## Anti-Patterns\n\n> 🚨 **Every failure verdict needs evidence — no \"Likely flaky\" without proof.** Each row in your summary table must cite a specific source: known issue number, Build Analysis match, or target-branch verification. If Build Analysis didn't match it and you haven't verified the target branch, the verdict is **\"Unmatched — needs investigation\"**, not \"Likely flaky.\" A test that *looks* like it could be flaky is not the same as one you've *verified* is flaky.\n\n> ❌ **Don't label failures \"infrastructure\" without evidence.** Requires: Build Analysis match, identical failure on target branch, or confirmed outage. Exception: `tests-passed-reporter-failed` is genuinely infrastructure.\n\n> ❌ **Don't dismiss timed-out builds.** A build \"failed\" due to AzDO timeout can have 100% passing Helix work items. Check Helix job status before concluding failure.\n\n> ❌ **Missing packages on flow PRs ≠ infrastructure.** Flow PRs request *different* packages. Check *which* package and *why* before assuming feed delay.\n\n> ❌ **Don't present failures and known issues as separate lists.** Cross-reference them: for each `failedJobDetails` entry, state whether it matches a `knownIssues` entry or is unmatched. An `unclassified` failure can still match a known issue by error pattern.\n\n> ❌ **Don't say \"safe to retry\" with Build Analysis red.** Map each failing job to a specific known issue first.\n\n> ❌ **Don't execute `gh issue create` without explicit user approval.** Always present the draft command as text and ask the user to confirm before running it. This applies to KBE issues and any other GitHub issue creation.\n\n> ❌ **Don't use raw REST APIs when higher-level tools are available.** Check your available tools for Azure DevOps and Helix operations first. REST API fallback is for when those tools are genuinely unavailable, not a first resort.\n\n## References\n\n- **Script modes & parameters**: [references\u002Fscript-modes.md](references\u002Fscript-modes.md)\n- **Failure interpretation**: [references\u002Ffailure-interpretation.md](references\u002Ffailure-interpretation.md)\n- **Recommendation generation**: [references\u002Frecommendation-generation.md](references\u002Frecommendation-generation.md)\n- **Analysis workflow (Steps 1–3)**: [references\u002Fanalysis-workflow.md](references\u002Fanalysis-workflow.md)\n- **Helix artifacts & binlogs**: [references\u002Fhelix-artifacts.md](references\u002Fhelix-artifacts.md)\n- **Binlog comparison**: For cross-build binlog diffs, use deep investigation techniques from [references\u002Fdelegation-patterns.md](references\u002Fdelegation-patterns.md)\n- **Build progression analysis**: [references\u002Fbuild-progression-analysis.md](references\u002Fbuild-progression-analysis.md)\n- **Subagent delegation**: [references\u002Fdelegation-patterns.md](references\u002Fdelegation-patterns.md)\n- **Azure CLI investigation**: [references\u002Fazure-cli.md](references\u002Fazure-cli.md)\n- **Manual investigation**: [references\u002Fmanual-investigation.md](references\u002Fmanual-investigation.md)\n- **SQL tracking**: [references\u002Fsql-tracking.md](references\u002Fsql-tracking.md)\n- **Known Build Error issue creation**: [references\u002Fkbe-issue-creation.md](references\u002Fkbe-issue-creation.md)\n- **AzDO\u002FHelix details**: [references\u002Fazdo-helix-reference.md](references\u002Fazdo-helix-reference.md)\n\n## Tips\n\n1. Get repo-specific CI guidance first — it gives you the investigation order, search patterns, and gotchas\n2. Check if same test fails on target branch before assuming transient\n3. Look for skip\u002Fquarantine attributes on known-flaky tests — common ones across dotnet repos include `[ActiveIssue]`, `[SkipOnHelix]`, `[QuarantinedTest]`, and `[ConditionalFact]`\u002F`[ConditionalTheory]` with skip conditions\n4. Search for related issues across dotnet repos when failures don't match known patterns\n5. \"Canceled\" ≠ \"Failed\" — canceled jobs may have recoverable Helix results. Helix data may persist even when AzDO builds have expired.\n",{"data":37,"body":38},{"name":4,"description":6},{"type":39,"children":40},"root",[41,50,56,98,108,118,123,137,144,195,205,220,226,260,265,277,283,306,452,476,482,496,506,516,526,536,564,574,592,598,619,657,667,673,709,732,746,781,819,833,855,869,875,1056,1062],{"type":42,"tag":43,"props":44,"children":46},"element","h1",{"id":45},"azure-devops-and-helix-ci-analysis",[47],{"type":48,"value":49},"text","Azure DevOps and Helix CI Analysis",{"type":42,"tag":51,"props":52,"children":53},"p",{},[54],{"type":48,"value":55},"Analyze CI build status and test failures in Azure DevOps and Helix for dotnet repositories (runtime, sdk, aspnetcore, roslyn, and more).",{"type":42,"tag":57,"props":58,"children":59},"blockquote",{},[60],{"type":42,"tag":51,"props":61,"children":62},{},[63,65,71,73,80,82,88,90,96],{"type":48,"value":64},"🚨 ",{"type":42,"tag":66,"props":67,"children":68},"strong",{},[69],{"type":48,"value":70},"NEVER",{"type":48,"value":72}," use ",{"type":42,"tag":74,"props":75,"children":77},"code",{"className":76},[],[78],{"type":48,"value":79},"gh pr review --approve",{"type":48,"value":81}," or ",{"type":42,"tag":74,"props":83,"children":85},{"className":84},[],[86],{"type":48,"value":87},"--request-changes",{"type":48,"value":89},". Only ",{"type":42,"tag":74,"props":91,"children":93},{"className":92},[],[94],{"type":48,"value":95},"--comment",{"type":48,"value":97}," is allowed. Approval and blocking are human-only actions.",{"type":42,"tag":51,"props":99,"children":100},{},[101,106],{"type":42,"tag":66,"props":102,"children":103},{},[104],{"type":48,"value":105},"Workflow",{"type":48,"value":107},": Gather PR context (Step 0) → collect failure data → synthesize recommendations. The agent drives the investigation; tools provide the data.",{"type":42,"tag":51,"props":109,"children":110},{},[111,116],{"type":42,"tag":66,"props":112,"children":113},{},[114],{"type":48,"value":115},"Accessing services",{"type":48,"value":117},": Start with MCP tools if available. Get repo-specific CI guidance early — it provides the investigation workflow, tool selection, failure patterns, and classification algorithm for that repo. The guidance evolves with the toolset, so it always reflects current capabilities.",{"type":42,"tag":51,"props":119,"children":120},{},[121],{"type":48,"value":122},"If MCP tools aren't loaded, the Helix CLI tool provides the same capabilities via bash with progressive discovery.",{"type":42,"tag":51,"props":124,"children":125},{},[126,128,135],{"type":48,"value":127},"For AzDO, multiple tool sets may exist for different organizations — match the org in the build URL to the correct tools (see ",{"type":42,"tag":129,"props":130,"children":132},"a",{"href":131},"references\u002Fazdo-helix-reference.md#azure-devops-organizations",[133],{"type":48,"value":134},"references\u002Fazdo-helix-reference.md",{"type":48,"value":136},"). If queries return null, check the org before trying other approaches. For complex investigations, track what you've tried in SQL to avoid repeating failed approaches.",{"type":42,"tag":138,"props":139,"children":141},"h2",{"id":140},"when-to-use-this-skill",[142],{"type":48,"value":143},"When to Use This Skill",{"type":42,"tag":145,"props":146,"children":147},"ul",{},[148,154,159,164,185,190],{"type":42,"tag":149,"props":150,"children":151},"li",{},[152],{"type":48,"value":153},"Checking CI status (\"is CI passing?\", \"why is CI red?\")",{"type":42,"tag":149,"props":155,"children":156},{},[157],{"type":48,"value":158},"Investigating CI failures or determining merge readiness",{"type":42,"tag":149,"props":160,"children":161},{},[162],{"type":48,"value":163},"Debugging Helix test issues or build errors",{"type":42,"tag":149,"props":165,"children":166},{},[167,169,175,177,183],{"type":48,"value":168},"URLs containing ",{"type":42,"tag":74,"props":170,"children":172},{"className":171},[],[173],{"type":48,"value":174},"dev.azure.com",{"type":48,"value":176},", ",{"type":42,"tag":74,"props":178,"children":180},{"className":179},[],[181],{"type":48,"value":182},"helix.dot.net",{"type":48,"value":184},", or GitHub PR links with failing checks",{"type":42,"tag":149,"props":186,"children":187},{},[188],{"type":48,"value":189},"Questions like \"retry CI\", \"rerun tests\", \"test failures\", \"checks failing\"",{"type":42,"tag":149,"props":191,"children":192},{},[193],{"type":48,"value":194},"Investigating canceled or timed-out jobs for recoverable results",{"type":42,"tag":51,"props":196,"children":197},{},[198,203],{"type":42,"tag":66,"props":199,"children":200},{},[201],{"type":48,"value":202},"Not for",{"type":48,"value":204},": GitHub Actions workflows, non-Helix repos, or build performance (use binlog analysis).",{"type":42,"tag":57,"props":206,"children":207},{},[208],{"type":42,"tag":51,"props":209,"children":210},{},[211,213,218],{"type":48,"value":212},"💡 ",{"type":42,"tag":66,"props":214,"children":215},{},[216],{"type":48,"value":217},"Per-repo CI patterns differ significantly.",{"type":48,"value":219}," Get repo-specific guidance early — it tells you which tools to use, what log patterns to search for, and what gotchas to expect. This is the fastest path and prevents wasted calls.",{"type":42,"tag":138,"props":221,"children":223},{"id":222},"quick-start",[224],{"type":48,"value":225},"Quick Start",{"type":42,"tag":227,"props":228,"children":229},"ol",{},[230,240,250],{"type":42,"tag":149,"props":231,"children":232},{},[233,238],{"type":42,"tag":66,"props":234,"children":235},{},[236],{"type":48,"value":237},"Get repo-specific CI guidance",{"type":48,"value":239}," — investigation workflow, tool selection, search patterns, and failure classification for that repo",{"type":42,"tag":149,"props":241,"children":242},{},[243,248],{"type":42,"tag":66,"props":244,"children":245},{},[246],{"type":48,"value":247},"Find builds",{"type":48,"value":249}," for the PR or use a build ID directly",{"type":42,"tag":149,"props":251,"children":252},{},[253,258],{"type":42,"tag":66,"props":254,"children":255},{},[256],{"type":48,"value":257},"Follow the investigation order",{"type":48,"value":259}," from the guidance — it tells you what to check and in what sequence",{"type":42,"tag":51,"props":261,"children":262},{},[263],{"type":48,"value":264},"If MCP tools aren't available, the Helix CLI tool provides the same capabilities via bash. A legacy PowerShell script is also available for environments that support it.",{"type":42,"tag":51,"props":266,"children":267},{},[268,270,275],{"type":48,"value":269},"For full parameter reference and mode details, see ",{"type":42,"tag":129,"props":271,"children":273},{"href":272},"references\u002Fscript-modes.md",[274],{"type":48,"value":272},{"type":48,"value":276},".",{"type":42,"tag":138,"props":278,"children":280},{"id":279},"step-0-gather-context-before-running-anything",[281],{"type":48,"value":282},"Step 0: Gather Context (before running anything)",{"type":42,"tag":227,"props":284,"children":285},{},[286,296],{"type":42,"tag":149,"props":287,"children":288},{},[289,294],{"type":42,"tag":66,"props":290,"children":291},{},[292],{"type":48,"value":293},"Read PR metadata",{"type":48,"value":295}," — title, description, author, labels, linked issues",{"type":42,"tag":149,"props":297,"children":298},{},[299,304],{"type":42,"tag":66,"props":300,"children":301},{},[302],{"type":48,"value":303},"Classify the PR type",{"type":48,"value":305},":",{"type":42,"tag":307,"props":308,"children":309},"table",{},[310,334],{"type":42,"tag":311,"props":312,"children":313},"thead",{},[314],{"type":42,"tag":315,"props":316,"children":317},"tr",{},[318,324,329],{"type":42,"tag":319,"props":320,"children":321},"th",{},[322],{"type":48,"value":323},"PR Type",{"type":42,"tag":319,"props":325,"children":326},{},[327],{"type":48,"value":328},"How to detect",{"type":42,"tag":319,"props":330,"children":331},{},[332],{"type":48,"value":333},"Interpretation shift",{"type":42,"tag":335,"props":336,"children":337},"tbody",{},[338,360,389,410,431],{"type":42,"tag":315,"props":339,"children":340},{},[341,350,355],{"type":42,"tag":342,"props":343,"children":344},"td",{},[345],{"type":42,"tag":66,"props":346,"children":347},{},[348],{"type":48,"value":349},"Code PR",{"type":42,"tag":342,"props":351,"children":352},{},[353],{"type":48,"value":354},"Human author, code changes",{"type":42,"tag":342,"props":356,"children":357},{},[358],{"type":48,"value":359},"Failures likely relate to the changes",{"type":42,"tag":315,"props":361,"children":362},{},[363,371,384],{"type":42,"tag":342,"props":364,"children":365},{},[366],{"type":42,"tag":66,"props":367,"children":368},{},[369],{"type":48,"value":370},"Flow\u002FCodeflow PR",{"type":42,"tag":342,"props":372,"children":373},{},[374,376,382],{"type":48,"value":375},"Author is ",{"type":42,"tag":74,"props":377,"children":379},{"className":378},[],[380],{"type":48,"value":381},"dotnet-maestro[bot]",{"type":48,"value":383},", \"Update dependencies\"",{"type":42,"tag":342,"props":385,"children":386},{},[387],{"type":48,"value":388},"Missing packages may be behavioral, not infrastructure",{"type":42,"tag":315,"props":390,"children":391},{},[392,400,405],{"type":42,"tag":342,"props":393,"children":394},{},[395],{"type":42,"tag":66,"props":396,"children":397},{},[398],{"type":48,"value":399},"Backport",{"type":42,"tag":342,"props":401,"children":402},{},[403],{"type":48,"value":404},"Title mentions \"backport\", targets release branch",{"type":42,"tag":342,"props":406,"children":407},{},[408],{"type":48,"value":409},"Check if test exists on target branch",{"type":42,"tag":315,"props":411,"children":412},{},[413,421,426],{"type":42,"tag":342,"props":414,"children":415},{},[416],{"type":42,"tag":66,"props":417,"children":418},{},[419],{"type":48,"value":420},"Merge PR",{"type":42,"tag":342,"props":422,"children":423},{},[424],{"type":48,"value":425},"Merging between branches",{"type":42,"tag":342,"props":427,"children":428},{},[429],{"type":48,"value":430},"Conflicts cause failures, not individual changes",{"type":42,"tag":315,"props":432,"children":433},{},[434,442,447],{"type":42,"tag":342,"props":435,"children":436},{},[437],{"type":42,"tag":66,"props":438,"children":439},{},[440],{"type":48,"value":441},"Dependency update",{"type":42,"tag":342,"props":443,"children":444},{},[445],{"type":48,"value":446},"Bumps package versions, global.json",{"type":42,"tag":342,"props":448,"children":449},{},[450],{"type":48,"value":451},"Build failures often trace to the dependency",{"type":42,"tag":227,"props":453,"children":455},{"start":454},3,[456,466],{"type":42,"tag":149,"props":457,"children":458},{},[459,464],{"type":42,"tag":66,"props":460,"children":461},{},[462],{"type":48,"value":463},"Check existing comments",{"type":48,"value":465}," — has someone already diagnosed failures or is a retry pending?",{"type":42,"tag":149,"props":467,"children":468},{},[469,474],{"type":42,"tag":66,"props":470,"children":471},{},[472],{"type":48,"value":473},"Note the changed files",{"type":48,"value":475}," — you'll use these for failure correlation",{"type":42,"tag":138,"props":477,"children":479},{"id":478},"after-data-collection-synthesize",[480],{"type":48,"value":481},"After Data Collection: Synthesize",{"type":42,"tag":57,"props":483,"children":484},{},[485],{"type":42,"tag":51,"props":486,"children":487},{},[488,489,494],{"type":48,"value":64},{"type":42,"tag":66,"props":490,"children":491},{},[492],{"type":48,"value":493},"Don't re-fetch data you already have.",{"type":48,"value":495}," Only make additional calls for deeper investigation (Helix log searches, binlog analysis, build progression).",{"type":42,"tag":51,"props":497,"children":498},{},[499,504],{"type":42,"tag":66,"props":500,"children":501},{},[502],{"type":48,"value":503},"Classify each failure.",{"type":48,"value":505}," Determine whether it's a build error, test failure, crash, timeout, or infrastructure issue. Exit codes, log patterns, and Helix work item state all contribute — the repo-specific CI guidance includes a classification algorithm with the patterns and recommended next steps for each category. Crashes (exit code -4, 139, 134) don't always mean tests failed — check for recoverable test results before concluding.",{"type":42,"tag":51,"props":507,"children":508},{},[509,514],{"type":42,"tag":66,"props":510,"children":511},{},[512],{"type":48,"value":513},"Cross-reference with known issues.",{"type":48,"value":515}," Check which failures are already matched by Build Analysis — green means all failures are accounted for, red means some are unmatched. For each unmatched failure, search for related known issues by error message, test name, or job type. The user needs a per-failure verdict, not two separate lists.",{"type":42,"tag":51,"props":517,"children":518},{},[519,524],{"type":42,"tag":66,"props":520,"children":521},{},[522],{"type":48,"value":523},"Correlate with PR changes.",{"type":48,"value":525}," If the same files appear in both the PR diff and the failure messages, the failure is likely PR-related. If not, check whether the same test fails on the target branch — that distinguishes pre-existing flakes from regressions.",{"type":42,"tag":51,"props":527,"children":528},{},[529,534],{"type":42,"tag":66,"props":530,"children":531},{},[532],{"type":48,"value":533},"Verify before claiming.",{"type":48,"value":535}," Don't call it \"infrastructure\" without a Build Analysis match or target-branch verification. Don't call it \"safe to retry\" unless ALL failures are accounted for.",{"type":42,"tag":57,"props":537,"children":538},{},[539],{"type":42,"tag":51,"props":540,"children":541},{},[542,543,548,550,556,558,563],{"type":48,"value":64},{"type":42,"tag":66,"props":544,"children":545},{},[546],{"type":48,"value":547},"Check build progression on multi-commit PRs.",{"type":48,"value":549}," If the PR has multiple commits, query AzDO for builds on ",{"type":42,"tag":74,"props":551,"children":553},{"className":552},[],[554],{"type":48,"value":555},"refs\u002Fpull\u002F{PR}\u002Fmerge",{"type":48,"value":557}," (sorted by queue time, top 10-20). Present a progression table showing which builds passed\u002Ffailed at which SHAs — this narrows failures to the commit that introduced them. See ",{"type":42,"tag":129,"props":559,"children":561},{"href":560},"references\u002Fbuild-progression-analysis.md",[562],{"type":48,"value":560},{"type":48,"value":276},{"type":42,"tag":51,"props":565,"children":566},{},[567,569],{"type":48,"value":568},"For interpreting error categories, crash recovery, and canceled jobs: ",{"type":42,"tag":129,"props":570,"children":572},{"href":571},"references\u002Ffailure-interpretation.md",[573],{"type":48,"value":571},{"type":42,"tag":51,"props":575,"children":576},{},[577,579,585,587],{"type":48,"value":578},"For generating recommendations from ",{"type":42,"tag":74,"props":580,"children":582},{"className":581},[],[583],{"type":48,"value":584},"[CI_ANALYSIS_SUMMARY]",{"type":48,"value":586}," JSON: ",{"type":42,"tag":129,"props":588,"children":590},{"href":589},"references\u002Frecommendation-generation.md",[591],{"type":48,"value":589},{"type":42,"tag":138,"props":593,"children":595},{"id":594},"presenting-results",[596],{"type":48,"value":597},"Presenting Results",{"type":42,"tag":57,"props":599,"children":600},{},[601],{"type":42,"tag":51,"props":602,"children":603},{},[604,605,610,612,617],{"type":48,"value":64},{"type":42,"tag":66,"props":606,"children":607},{},[608],{"type":48,"value":609},"Keep tables narrow — 4 short columns max (# | Job | Verdict | Issue).",{"type":48,"value":611}," Put error descriptions, work item lists, and evidence in ",{"type":42,"tag":66,"props":613,"children":614},{},[615],{"type":48,"value":616},"detail bullets below the table",{"type":48,"value":618},", not in cells. Wide tables wrap and become unreadable in terminals.",{"type":42,"tag":57,"props":620,"children":621},{},[622],{"type":42,"tag":51,"props":623,"children":624},{},[625,626,631,633,639,641,647,649,655],{"type":48,"value":64},{"type":42,"tag":66,"props":627,"children":628},{},[629],{"type":48,"value":630},"Use markdown links",{"type":48,"value":632}," for PRs (",{"type":42,"tag":74,"props":634,"children":636},{"className":635},[],[637],{"type":48,"value":638},"[#121195](url)",{"type":48,"value":640},"), builds (",{"type":42,"tag":74,"props":642,"children":644},{"className":643},[],[645],{"type":48,"value":646},"[Build 1305302](url)",{"type":48,"value":648},"), and jobs (",{"type":42,"tag":74,"props":650,"children":652},{"className":651},[],[653],{"type":48,"value":654},"[job name](azdo-job-url)",{"type":48,"value":656},"). The script output and MCP tools provide URLs — thread them through.",{"type":42,"tag":51,"props":658,"children":659},{},[660,662,666],{"type":48,"value":661},"Lead with a 1-2 sentence verdict, then the summary table, then detail bullets (one per failure), then recommended actions. For the full format example: ",{"type":42,"tag":129,"props":663,"children":664},{"href":589},[665],{"type":48,"value":589},{"type":48,"value":276},{"type":42,"tag":138,"props":668,"children":670},{"id":669},"anti-patterns",[671],{"type":48,"value":672},"Anti-Patterns",{"type":42,"tag":57,"props":674,"children":675},{},[676],{"type":42,"tag":51,"props":677,"children":678},{},[679,680,685,687,692,694,700,702,707],{"type":48,"value":64},{"type":42,"tag":66,"props":681,"children":682},{},[683],{"type":48,"value":684},"Every failure verdict needs evidence — no \"Likely flaky\" without proof.",{"type":48,"value":686}," Each row in your summary table must cite a specific source: known issue number, Build Analysis match, or target-branch verification. If Build Analysis didn't match it and you haven't verified the target branch, the verdict is ",{"type":42,"tag":66,"props":688,"children":689},{},[690],{"type":48,"value":691},"\"Unmatched — needs investigation\"",{"type":48,"value":693},", not \"Likely flaky.\" A test that ",{"type":42,"tag":695,"props":696,"children":697},"em",{},[698],{"type":48,"value":699},"looks",{"type":48,"value":701}," like it could be flaky is not the same as one you've ",{"type":42,"tag":695,"props":703,"children":704},{},[705],{"type":48,"value":706},"verified",{"type":48,"value":708}," is flaky.",{"type":42,"tag":57,"props":710,"children":711},{},[712],{"type":42,"tag":51,"props":713,"children":714},{},[715,717,722,724,730],{"type":48,"value":716},"❌ ",{"type":42,"tag":66,"props":718,"children":719},{},[720],{"type":48,"value":721},"Don't label failures \"infrastructure\" without evidence.",{"type":48,"value":723}," Requires: Build Analysis match, identical failure on target branch, or confirmed outage. Exception: ",{"type":42,"tag":74,"props":725,"children":727},{"className":726},[],[728],{"type":48,"value":729},"tests-passed-reporter-failed",{"type":48,"value":731}," is genuinely infrastructure.",{"type":42,"tag":57,"props":733,"children":734},{},[735],{"type":42,"tag":51,"props":736,"children":737},{},[738,739,744],{"type":48,"value":716},{"type":42,"tag":66,"props":740,"children":741},{},[742],{"type":48,"value":743},"Don't dismiss timed-out builds.",{"type":48,"value":745}," A build \"failed\" due to AzDO timeout can have 100% passing Helix work items. Check Helix job status before concluding failure.",{"type":42,"tag":57,"props":747,"children":748},{},[749],{"type":42,"tag":51,"props":750,"children":751},{},[752,753,758,760,765,767,772,774,779],{"type":48,"value":716},{"type":42,"tag":66,"props":754,"children":755},{},[756],{"type":48,"value":757},"Missing packages on flow PRs ≠ infrastructure.",{"type":48,"value":759}," Flow PRs request ",{"type":42,"tag":695,"props":761,"children":762},{},[763],{"type":48,"value":764},"different",{"type":48,"value":766}," packages. Check ",{"type":42,"tag":695,"props":768,"children":769},{},[770],{"type":48,"value":771},"which",{"type":48,"value":773}," package and ",{"type":42,"tag":695,"props":775,"children":776},{},[777],{"type":48,"value":778},"why",{"type":48,"value":780}," before assuming feed delay.",{"type":42,"tag":57,"props":782,"children":783},{},[784],{"type":42,"tag":51,"props":785,"children":786},{},[787,788,793,795,801,803,809,811,817],{"type":48,"value":716},{"type":42,"tag":66,"props":789,"children":790},{},[791],{"type":48,"value":792},"Don't present failures and known issues as separate lists.",{"type":48,"value":794}," Cross-reference them: for each ",{"type":42,"tag":74,"props":796,"children":798},{"className":797},[],[799],{"type":48,"value":800},"failedJobDetails",{"type":48,"value":802}," entry, state whether it matches a ",{"type":42,"tag":74,"props":804,"children":806},{"className":805},[],[807],{"type":48,"value":808},"knownIssues",{"type":48,"value":810}," entry or is unmatched. An ",{"type":42,"tag":74,"props":812,"children":814},{"className":813},[],[815],{"type":48,"value":816},"unclassified",{"type":48,"value":818}," failure can still match a known issue by error pattern.",{"type":42,"tag":57,"props":820,"children":821},{},[822],{"type":42,"tag":51,"props":823,"children":824},{},[825,826,831],{"type":48,"value":716},{"type":42,"tag":66,"props":827,"children":828},{},[829],{"type":48,"value":830},"Don't say \"safe to retry\" with Build Analysis red.",{"type":48,"value":832}," Map each failing job to a specific known issue first.",{"type":42,"tag":57,"props":834,"children":835},{},[836],{"type":42,"tag":51,"props":837,"children":838},{},[839,840,853],{"type":48,"value":716},{"type":42,"tag":66,"props":841,"children":842},{},[843,845,851],{"type":48,"value":844},"Don't execute ",{"type":42,"tag":74,"props":846,"children":848},{"className":847},[],[849],{"type":48,"value":850},"gh issue create",{"type":48,"value":852}," without explicit user approval.",{"type":48,"value":854}," Always present the draft command as text and ask the user to confirm before running it. This applies to KBE issues and any other GitHub issue creation.",{"type":42,"tag":57,"props":856,"children":857},{},[858],{"type":42,"tag":51,"props":859,"children":860},{},[861,862,867],{"type":48,"value":716},{"type":42,"tag":66,"props":863,"children":864},{},[865],{"type":48,"value":866},"Don't use raw REST APIs when higher-level tools are available.",{"type":48,"value":868}," Check your available tools for Azure DevOps and Helix operations first. REST API fallback is for when those tools are genuinely unavailable, not a first resort.",{"type":42,"tag":138,"props":870,"children":872},{"id":871},"references",[873],{"type":48,"value":874},"References",{"type":42,"tag":145,"props":876,"children":877},{},[878,892,905,918,932,946,961,974,987,1001,1015,1029,1043],{"type":42,"tag":149,"props":879,"children":880},{},[881,886,888],{"type":42,"tag":66,"props":882,"children":883},{},[884],{"type":48,"value":885},"Script modes & parameters",{"type":48,"value":887},": ",{"type":42,"tag":129,"props":889,"children":890},{"href":272},[891],{"type":48,"value":272},{"type":42,"tag":149,"props":893,"children":894},{},[895,900,901],{"type":42,"tag":66,"props":896,"children":897},{},[898],{"type":48,"value":899},"Failure interpretation",{"type":48,"value":887},{"type":42,"tag":129,"props":902,"children":903},{"href":571},[904],{"type":48,"value":571},{"type":42,"tag":149,"props":906,"children":907},{},[908,913,914],{"type":42,"tag":66,"props":909,"children":910},{},[911],{"type":48,"value":912},"Recommendation generation",{"type":48,"value":887},{"type":42,"tag":129,"props":915,"children":916},{"href":589},[917],{"type":48,"value":589},{"type":42,"tag":149,"props":919,"children":920},{},[921,926,927],{"type":42,"tag":66,"props":922,"children":923},{},[924],{"type":48,"value":925},"Analysis workflow (Steps 1–3)",{"type":48,"value":887},{"type":42,"tag":129,"props":928,"children":930},{"href":929},"references\u002Fanalysis-workflow.md",[931],{"type":48,"value":929},{"type":42,"tag":149,"props":933,"children":934},{},[935,940,941],{"type":42,"tag":66,"props":936,"children":937},{},[938],{"type":48,"value":939},"Helix artifacts & binlogs",{"type":48,"value":887},{"type":42,"tag":129,"props":942,"children":944},{"href":943},"references\u002Fhelix-artifacts.md",[945],{"type":48,"value":943},{"type":42,"tag":149,"props":947,"children":948},{},[949,954,956],{"type":42,"tag":66,"props":950,"children":951},{},[952],{"type":48,"value":953},"Binlog comparison",{"type":48,"value":955},": For cross-build binlog diffs, use deep investigation techniques from ",{"type":42,"tag":129,"props":957,"children":959},{"href":958},"references\u002Fdelegation-patterns.md",[960],{"type":48,"value":958},{"type":42,"tag":149,"props":962,"children":963},{},[964,969,970],{"type":42,"tag":66,"props":965,"children":966},{},[967],{"type":48,"value":968},"Build progression analysis",{"type":48,"value":887},{"type":42,"tag":129,"props":971,"children":972},{"href":560},[973],{"type":48,"value":560},{"type":42,"tag":149,"props":975,"children":976},{},[977,982,983],{"type":42,"tag":66,"props":978,"children":979},{},[980],{"type":48,"value":981},"Subagent delegation",{"type":48,"value":887},{"type":42,"tag":129,"props":984,"children":985},{"href":958},[986],{"type":48,"value":958},{"type":42,"tag":149,"props":988,"children":989},{},[990,995,996],{"type":42,"tag":66,"props":991,"children":992},{},[993],{"type":48,"value":994},"Azure CLI investigation",{"type":48,"value":887},{"type":42,"tag":129,"props":997,"children":999},{"href":998},"references\u002Fazure-cli.md",[1000],{"type":48,"value":998},{"type":42,"tag":149,"props":1002,"children":1003},{},[1004,1009,1010],{"type":42,"tag":66,"props":1005,"children":1006},{},[1007],{"type":48,"value":1008},"Manual investigation",{"type":48,"value":887},{"type":42,"tag":129,"props":1011,"children":1013},{"href":1012},"references\u002Fmanual-investigation.md",[1014],{"type":48,"value":1012},{"type":42,"tag":149,"props":1016,"children":1017},{},[1018,1023,1024],{"type":42,"tag":66,"props":1019,"children":1020},{},[1021],{"type":48,"value":1022},"SQL tracking",{"type":48,"value":887},{"type":42,"tag":129,"props":1025,"children":1027},{"href":1026},"references\u002Fsql-tracking.md",[1028],{"type":48,"value":1026},{"type":42,"tag":149,"props":1030,"children":1031},{},[1032,1037,1038],{"type":42,"tag":66,"props":1033,"children":1034},{},[1035],{"type":48,"value":1036},"Known Build Error issue creation",{"type":48,"value":887},{"type":42,"tag":129,"props":1039,"children":1041},{"href":1040},"references\u002Fkbe-issue-creation.md",[1042],{"type":48,"value":1040},{"type":42,"tag":149,"props":1044,"children":1045},{},[1046,1051,1052],{"type":42,"tag":66,"props":1047,"children":1048},{},[1049],{"type":48,"value":1050},"AzDO\u002FHelix details",{"type":48,"value":887},{"type":42,"tag":129,"props":1053,"children":1054},{"href":134},[1055],{"type":48,"value":134},{"type":42,"tag":138,"props":1057,"children":1059},{"id":1058},"tips",[1060],{"type":48,"value":1061},"Tips",{"type":42,"tag":227,"props":1063,"children":1064},{},[1065,1070,1075,1118,1123],{"type":42,"tag":149,"props":1066,"children":1067},{},[1068],{"type":48,"value":1069},"Get repo-specific CI guidance first — it gives you the investigation order, search patterns, and gotchas",{"type":42,"tag":149,"props":1071,"children":1072},{},[1073],{"type":48,"value":1074},"Check if same test fails on target branch before assuming transient",{"type":42,"tag":149,"props":1076,"children":1077},{},[1078,1080,1086,1087,1093,1094,1100,1102,1108,1110,1116],{"type":48,"value":1079},"Look for skip\u002Fquarantine attributes on known-flaky tests — common ones across dotnet repos include ",{"type":42,"tag":74,"props":1081,"children":1083},{"className":1082},[],[1084],{"type":48,"value":1085},"[ActiveIssue]",{"type":48,"value":176},{"type":42,"tag":74,"props":1088,"children":1090},{"className":1089},[],[1091],{"type":48,"value":1092},"[SkipOnHelix]",{"type":48,"value":176},{"type":42,"tag":74,"props":1095,"children":1097},{"className":1096},[],[1098],{"type":48,"value":1099},"[QuarantinedTest]",{"type":48,"value":1101},", and ",{"type":42,"tag":74,"props":1103,"children":1105},{"className":1104},[],[1106],{"type":48,"value":1107},"[ConditionalFact]",{"type":48,"value":1109},"\u002F",{"type":42,"tag":74,"props":1111,"children":1113},{"className":1112},[],[1114],{"type":48,"value":1115},"[ConditionalTheory]",{"type":48,"value":1117}," with skip conditions",{"type":42,"tag":149,"props":1119,"children":1120},{},[1121],{"type":48,"value":1122},"Search for related issues across dotnet repos when failures don't match known patterns",{"type":42,"tag":149,"props":1124,"children":1125},{},[1126],{"type":48,"value":1127},"\"Canceled\" ≠ \"Failed\" — canceled jobs may have recoverable Helix results. Helix data may persist even when AzDO builds have expired.",{"items":1129,"total":25},[1130,1147,1160,1167,1180,1197,1207],{"slug":1131,"name":1131,"fn":1132,"description":1133,"org":1134,"tags":1135,"stars":25,"repoUrl":26,"updatedAt":1146},"binskim-analysis","investigate BinSkim SDL security findings","Investigate BinSkim SDL findings from official pipelines — understand Guardian filtering, compare raw vs merged SARIF, decode portal results, and determine fix ownership. Use when asked about SDL scan results, portal findings, Guardian filtering, rule meanings, or discrepancies between local and official results. Also use when asked \"why does the portal show X\", \"what's filtered\", \"explain Guardian\", \"investigate SDL findings\", \"portal BA2008\", \"binskim failures in pipeline\", or \"what rules are required\". DO NOT USE FOR: running BinSkim locally (use binskim-scan), source code analysis (use CodeQL), or credential scanning (use CredScan).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1136,1137,1140,1143],{"name":17,"slug":18,"type":15},{"name":1138,"slug":1139,"type":15},"Audit","audit",{"name":1141,"slug":1142,"type":15},"Code Analysis","code-analysis",{"name":1144,"slug":1145,"type":15},"Security","security","2026-07-12T08:23:11.212231",{"slug":1148,"name":1148,"fn":1149,"description":1150,"org":1151,"tags":1152,"stars":25,"repoUrl":26,"updatedAt":1159},"binskim-scan","run BinSkim binary security analysis","Run BinSkim binary security analysis locally against a dotnet repository. Use when asked to scan binaries, check BinSkim compliance, verify a fix for a rule violation, or run a local SDL scan. Also use when asked \"run binskim\", \"binary security scan\", \"scan binaries\", \"check binskim\", \"verify my fix\", \"repro BA2008 locally\", or \"verify BA2008 fix\". DO NOT USE FOR: investigating official pipeline results or portal findings (use binskim-analysis), source code analysis (use CodeQL), credential scanning (use CredScan), or general build\u002Ftest failures (use ci-analysis).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1153,1154,1157,1158],{"name":17,"slug":18,"type":15},{"name":1155,"slug":1156,"type":15},"CLI","cli",{"name":1141,"slug":1142,"type":15},{"name":1144,"slug":1145,"type":15},"2026-07-12T08:23:09.911458",{"slug":4,"name":4,"fn":5,"description":6,"org":1161,"tags":1162,"stars":25,"repoUrl":26,"updatedAt":27},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1163,1164,1165,1166],{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"name":23,"slug":24,"type":15},{"slug":1168,"name":1168,"fn":1169,"description":1170,"org":1171,"tags":1172,"stars":25,"repoUrl":26,"updatedAt":1179},"ci-crash-dump","debug CI crash dumps","Download and debug crash dumps from CI test failures in dotnet repositories. Use when a CI test crashed (not just failed), when the user wants to debug a crash dump from a PR or build, or when asked \"debug dump\", \"download dump\", \"crash dump from CI\", \"test crashed\", \"analyze crash in PR\", or \"why did the test crash\". DO NOT USE FOR: test failures that are not crashes (use ci-analysis), build failures, performance analysis, or analyzing dumps you already have locally.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1173,1174,1175,1176],{"name":17,"slug":18,"type":15},{"name":20,"slug":21,"type":15},{"name":23,"slug":24,"type":15},{"name":1177,"slug":1178,"type":15},"Testing","testing","2026-07-12T08:21:56.945844",{"slug":1181,"name":1181,"fn":1182,"description":1183,"org":1184,"tags":1185,"stars":25,"repoUrl":26,"updatedAt":1196},"flow-analysis","analyze VMR codeflow health","Analyze VMR codeflow health using maestro MCP tools and GitHub MCP tools. USE FOR: investigating stale codeflow PRs, checking if fixes have flowed through the VMR pipeline, debugging dependency update issues, checking overall flow status for a repo, diagnosing why backflow PRs are missing or blocked, subscription health, build freshness, URLs containing dotnet-maestro or \"Source code updates from dotnet\u002Fdotnet\". DO NOT USE FOR: CI build failures (use ci-analysis skill), code review (use code-review skill), general PR investigation without codeflow context, tracing whether a specific commit\u002FPR has reached another repo (use flow-tracing skill). INVOKES: maestro and GitHub MCP tools, flow-health.cs script.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1186,1187,1190,1193],{"name":20,"slug":21,"type":15},{"name":1188,"slug":1189,"type":15},"Engineering","engineering",{"name":1191,"slug":1192,"type":15},"GitHub","github",{"name":1194,"slug":1195,"type":15},"MCP","mcp","2026-07-12T08:21:53.151866",{"slug":1198,"name":1198,"fn":1199,"description":1200,"org":1201,"tags":1202,"stars":25,"repoUrl":26,"updatedAt":1206},"flow-tracing","trace .NET dependency flow in VMR","Trace dependency flow across .NET repos through the VMR pipeline. USE FOR: checking if a PR\u002Fcommit from repo A has reached repo B, finding what runtime SHA is in an SDK build, tracing dependency versions through the VMR, checking if a commit is included in an SDK build, decoding SDK version strings, \"has my fix reached runtime\", \"did roslyn#80873 flow to runtime\", \"what SHA is in SDK version X\", cross-repo dependency tracing, mapping SDK versions to VMR commits. DO NOT USE FOR: codeflow PR health or staleness (use flow-analysis skill), CI build failures (use ci-analysis skill). INVOKES: maestro and GitHub MCP tools, Get-SdkVersionTrace.ps1 script.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1203],{"name":1204,"slug":1205,"type":15},"Data Pipeline","data-pipeline","2026-07-12T08:21:55.689056",{"slug":1208,"name":1208,"fn":1209,"description":1210,"org":1211,"tags":1212,"stars":25,"repoUrl":26,"updatedAt":1216},"helix-investigation","investigate Helix test failures","Deep-dive investigation of Helix test failures starting from AzDO build legs. USE FOR: investigating recurring Helix test failures, downloading and analyzing Helix console logs, comparing passing vs failing runs, identifying machine-specific issues, XHarness timeout analysis, Android emulator DEVICE_NOT_FOUND errors, bulk failure aggregation across legs, \"why does this test fail on some machines\", \"top 5 failing tests in the last 2 days\", \"download helix logs for build X\", \"compare passing and failing helix runs\", \"what are the most common failures\". DO NOT USE FOR: high-level CI status checks (use ci-analysis), codeflow PRs (use flow-analysis). INVOKES: Helix and AzDO MCP tools, curl, gh CLI.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1213,1214,1215],{"name":23,"slug":24,"type":15},{"name":1188,"slug":1189,"type":15},{"name":1177,"slug":1178,"type":15},"2026-07-12T08:21:46.445586",{"items":1218,"total":1377},[1219,1233,1246,1261,1279,1291,1311,1321,1333,1343,1356,1367],{"slug":1220,"name":1220,"fn":1221,"description":1222,"org":1223,"tags":1224,"stars":1230,"repoUrl":1231,"updatedAt":1232},"multithreaded-task-migration","migrate MSBuild tasks to multithreaded mode","Guide for migrating MSBuild tasks to multithreaded mode support, including compatibility red-team review. Use this when converting tasks to thread-safe versions, implementing IMultiThreadableTask, adding TaskEnvironment support, or auditing migrations for behavioral compatibility.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1225,1226,1227],{"name":17,"slug":18,"type":15},{"name":1188,"slug":1189,"type":15},{"name":1228,"slug":1229,"type":15},"Performance","performance",5535,"https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fmsbuild","2026-07-22T05:37:33.965588",{"slug":1234,"name":1234,"fn":1235,"description":1236,"org":1237,"tags":1238,"stars":1243,"repoUrl":1244,"updatedAt":1245},"analyzing-dotnet-performance","analyze .NET code for performance anti-patterns","Scans .NET code for ~50 performance anti-patterns across async, memory, strings, collections, LINQ, regex, serialization, and I\u002FO with tiered severity classification. Use when analyzing .NET code for optimization opportunities, reviewing hot paths, or auditing allocation-heavy patterns.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1239,1240,1241,1242],{"name":17,"slug":18,"type":15},{"name":1141,"slug":1142,"type":15},{"name":23,"slug":24,"type":15},{"name":1228,"slug":1229,"type":15},4576,"https:\u002F\u002Fgithub.com\u002Fdotnet\u002Fskills","2026-07-12T08:23:25.400375",{"slug":1247,"name":1247,"fn":1248,"description":1249,"org":1250,"tags":1251,"stars":1243,"repoUrl":1244,"updatedAt":1260},"android-tombstone-symbolication","symbolicate .NET runtime frames in Android tombstones","Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app crash from a tombstone, resolving native backtrace frames in libmonosgen-2.0.so or libcoreclr.so to .NET runtime source code, or investigating SIGABRT, SIGSEGV, or other native signals originating from the .NET runtime on Android. DO NOT USE FOR pure Java\u002FKotlin crashes, managed .NET exceptions that are already captured in logcat, or iOS crash logs. INVOKES Symbolicate-Tombstone.ps1 script, llvm-symbolizer, Microsoft symbol server.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1252,1253,1256,1257],{"name":17,"slug":18,"type":15},{"name":1254,"slug":1255,"type":15},"Android","android",{"name":23,"slug":24,"type":15},{"name":1258,"slug":1259,"type":15},"Microsoft","microsoft","2026-07-12T08:23:21.595572",{"slug":1262,"name":1262,"fn":1263,"description":1264,"org":1265,"tags":1266,"stars":1243,"repoUrl":1244,"updatedAt":1278},"apple-crash-symbolication","symbolicate .NET runtime frames in crash logs","Symbolicate .NET runtime frames in Apple platform .ips crash logs (iOS, tvOS, Mac Catalyst, macOS). Extracts UUIDs and addresses from the native backtrace, locates dSYM debug symbols, and runs atos to produce function names with source file and line numbers. Automatically downloads .dwarf symbols from the Microsoft symbol server using Mach-O UUIDs. USE FOR triaging a .NET MAUI or Mono app crash from an .ips file on any Apple platform, resolving native backtrace frames in libcoreclr or libmonosgen-2.0 to .NET runtime source code, retrieving .ips crash logs from a connected iOS device or iPhone, or investigating EXC_CRASH, EXC_BAD_ACCESS, SIGABRT, or SIGSEGV originating from the .NET runtime. DO NOT USE FOR pure Swift\u002FObjective-C crashes with no .NET components, or Android tombstone files. INVOKES Symbolicate-Crash.ps1 script, atos, dwarfdump, idevicecrashreport.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1267,1268,1269,1272,1275],{"name":17,"slug":18,"type":15},{"name":23,"slug":24,"type":15},{"name":1270,"slug":1271,"type":15},"iOS","ios",{"name":1273,"slug":1274,"type":15},"macOS","macos",{"name":1276,"slug":1277,"type":15},"Observability","observability","2026-07-12T08:23:20.369986",{"slug":1280,"name":1280,"fn":1281,"description":1282,"org":1283,"tags":1284,"stars":1243,"repoUrl":1244,"updatedAt":1290},"assertion-quality","evaluate assertion quality in test suites","Analyzes the variety and depth of assertions across test suites in any language. Use when the user asks to evaluate assertion quality, find shallow tests, identify assertion-free tests (no assertions or only trivial ones like Assert.IsNotNull \u002F toBeTruthy()), flag self-referential or tautological assertions, measure assertion diversity, or audit whether tests verify different facets of behavior. Polyglot: .NET, Python, TS\u002FJS, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, C++. DO NOT USE FOR: writing new tests (use code-testing-agent \u002F writing-mstest-tests), mutation reasoning about whether tests would catch a bug (use test-gap-analysis), or a general severity-ranked anti-pattern audit (use test-anti-patterns), fixing or rewriting assertions, or writing, fixing, or modernizing MSTest tests, assertions, or attributes (use writing-mstest-tests).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1285,1286,1289],{"name":1141,"slug":1142,"type":15},{"name":1287,"slug":1288,"type":15},"QA","qa",{"name":1177,"slug":1178,"type":15},"2026-07-12T08:23:51.277743",{"slug":1292,"name":1292,"fn":1293,"description":1294,"org":1295,"tags":1296,"stars":1243,"repoUrl":1244,"updatedAt":1310},"author-component","create and review Blazor components","Create or review Blazor components (.razor files) with correct architecture. USE FOR: writing new Blazor components that do NOT involve JavaScript interop, implementing parameters and EventCallback, RenderFragment slots, component lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable, CancellationToken, CSS isolation, code-behind. DO NOT USE FOR: creating new projects (use create-blazor-project), JavaScript interop or calling browser APIs from Blazor (use use-js-interop), forms and validation (use collect-user-input), prerendering issues (use support-prerendering), HTTP data fetching patterns (use fetch-and-send-data), coordinating state between unrelated components (use coordinate-components).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1297,1298,1301,1304,1307],{"name":17,"slug":18,"type":15},{"name":1299,"slug":1300,"type":15},"Blazor","blazor",{"name":1302,"slug":1303,"type":15},"C#","csharp",{"name":1305,"slug":1306,"type":15},"UI Components","ui-components",{"name":1308,"slug":1309,"type":15},"Web Development","web-development","2026-07-15T06:03:29.216359",{"slug":1312,"name":1312,"fn":1313,"description":1314,"org":1315,"tags":1316,"stars":1243,"repoUrl":1244,"updatedAt":1320},"binlog-failure-analysis","analyze MSBuild binary logs","Analyze MSBuild binary logs to diagnose build failures. USE FOR: build errors that are unclear from console output, diagnosing cascading failures across multi-project builds, tracing MSBuild target execution order, and generally any MSBuild build issues. Requires an existing .binlog file. DO NOT USE FOR: generating binlogs (use binlog-generation), non-MSBuild build systems.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1317,1318,1319],{"name":1141,"slug":1142,"type":15},{"name":23,"slug":24,"type":15},{"name":1258,"slug":1259,"type":15},"2026-07-12T08:21:34.637923",{"slug":1322,"name":1322,"fn":1323,"description":1324,"org":1325,"tags":1326,"stars":1243,"repoUrl":1244,"updatedAt":1332},"binlog-generation","generate MSBuild binary logs for diagnostics","Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. USE FOR: adding \u002Fbl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors or performance. Requires MSBuild 17.8+ \u002F .NET 8 SDK+ for {} placeholder; PowerShell needs -bl:{{}}. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake), analyzing an existing binlog (use binlog-failure-analysis instead).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1327,1330,1331],{"name":1328,"slug":1329,"type":15},"Build","build",{"name":23,"slug":24,"type":15},{"name":1188,"slug":1189,"type":15},"2026-07-19T05:38:19.340791",{"slug":1334,"name":1334,"fn":1335,"description":1336,"org":1337,"tags":1338,"stars":1243,"repoUrl":1244,"updatedAt":1342},"build-parallelism","optimize MSBuild build parallelism","Diagnose and fix under-parallelized MSBuild builds. USE WHEN a multi-project solution build is slower than expected, doesn't speed up when you add cores, pegs a single core while others idle, or you want to know why `-m` isn't helping. Note: `\u002Fmaxcpucount` default is 1 (sequential) — always pass `-m` for parallel builds. Covers finding the critical path (longest serial ProjectReference chain), graph build (`\u002Fgraph`), BuildInParallel, and solution filters (`.slnf`). DO NOT USE FOR: single-project builds, incremental issues (use incremental-build), compilation slowness inside one project (use build-perf-diagnostics), non-MSBuild build systems.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1339,1340,1341],{"name":17,"slug":18,"type":15},{"name":1188,"slug":1189,"type":15},{"name":1228,"slug":1229,"type":15},"2026-07-19T05:38:18.364937",{"slug":1344,"name":1344,"fn":1345,"description":1346,"org":1347,"tags":1348,"stars":1243,"repoUrl":1244,"updatedAt":1355},"build-perf-baseline","establish and optimize build performance baselines","Establish build performance baselines and apply systematic optimization techniques. USE FOR: diagnosing slow builds, establishing before\u002Fafter measurements (cold, warm, no-op scenarios), applying optimization strategies like MSBuild Server, static graph builds, artifacts output, and dependency graph trimming. Start here before diving into build-perf-diagnostics, incremental-build, or build-parallelism. DO NOT USE FOR: non-MSBuild build systems, detailed bottleneck analysis (use build-perf-diagnostics after baselining).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1349,1350,1353,1354],{"name":1188,"slug":1189,"type":15},{"name":1351,"slug":1352,"type":15},"Monitoring","monitoring",{"name":1228,"slug":1229,"type":15},{"name":1177,"slug":1178,"type":15},"2026-07-12T08:21:35.865649",{"slug":1357,"name":1357,"fn":1358,"description":1359,"org":1360,"tags":1361,"stars":1243,"repoUrl":1244,"updatedAt":1366},"build-perf-diagnostics","diagnose MSBuild build performance bottlenecks","Diagnose MSBuild build performance bottlenecks using binary log analysis. USE FOR: identifying why builds are slow by analyzing binlog performance summaries, detecting ResolveAssemblyReference (RAR) taking >5s, Roslyn analyzers consuming >30% of Csc time, single targets dominating >50% of build time, node utilization below 80%, excessive Copy tasks, NuGet restore running every build. Covers timeline analysis, Target\u002FTask Performance Summary interpretation, and 7 common bottleneck categories. Use after build-perf-baseline has established measurements. DO NOT USE FOR: establishing initial baselines (use build-perf-baseline first), fixing incremental build issues (use incremental-build), parallelism tuning (use build-parallelism), non-MSBuild build systems.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1362,1363,1364,1365],{"name":17,"slug":18,"type":15},{"name":23,"slug":24,"type":15},{"name":1188,"slug":1189,"type":15},{"name":1228,"slug":1229,"type":15},"2026-07-12T08:21:40.961722",{"slug":1368,"name":1368,"fn":1369,"description":1370,"org":1371,"tags":1372,"stars":1243,"repoUrl":1244,"updatedAt":1376},"check-bin-obj-clash","detect MSBuild output path conflicts","Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, or missing\u002Foverwritten outputs in multi-project or multi-targeting builds where bin\u002Fobj (or project.assets.json) collide. Common causes: shared OutputPath, missing AppendTargetFrameworkToOutputPath, extra global properties (e.g. PublishReadyToRun), or SetTargetFramework on a ProjectReference to a single-targeting project. DO NOT USE FOR: file access errors unrelated to MSBuild (OS-level locking), single-project single-TFM builds, non-MSBuild build systems.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1373,1374,1375],{"name":23,"slug":24,"type":15},{"name":1188,"slug":1189,"type":15},{"name":1287,"slug":1288,"type":15},"2026-07-19T05:38:14.336279",144]