Vendored (MIT) from dotnet/arcade-skills: .NET engineering-infrastructure CI/CD investigation. A ci-investigator orchestrator agent routes across 10 skills (Helix log analysis, Azure DevOps pipeline triage, binlog/crash-dump inspection, codeflow + dependency tracing, Maestro, known-issue history) and 4 MCP servers. Forked only to fix the manifest agents path for Claude Code's ./-prefixed component-path schema; upstream is unchanged otherwise.
6 on GitHubby .NET Team at Microsoftv0.1.0MITupdated 9 days ago
/
Plugin dotnet-dnceng from marketplace ancplua-claude-plugins in ANcpLua/ancplua-claude-plugins. Commands read from the repo's manifest — 8 days ago.
This plugin runs code on your machine — it starts local MCP servers. The exact commands are listed below; read them before installing.
What it installs
Skills (10)
binlog-failure-analysis
Analyze a failed Azure DevOps PR build by reusing the binlog that build already produced — instead of rebuilding locally. Use when an `azure-pipelines` check on a GitHub PR transitions to `failure` and you need a structured root-cause analysis posted back as a PR review. Downloads `PostBuildLogs_*`
ci-analysis
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
ci-crash-dump
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 d
flow-analysis
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
flow-tracing
Trace dependency flow across .NET repos through the VMR pipeline. USE FOR: checking if a PR/commit 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,
helix-investigation
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
known-issue-history
Analyze historical failure rates for Known Build Error issues by mining the edit history of issue bodies. Use when asked "when did this last fail", "failure history", "failure rate", "is this issue still active", "flaky test history", "known issue activity", or "most active known issues".
maestro-cli
Query Maestro/BAR dependency flow data using the mstro CLI tool via bash. USE FOR: subscription health checks, build flow tracing, codeflow status, channel discovery, triggering subscription updates — when MCP tools aren't loaded or when scripting with JSON output and jq. Also use when investigating
pipeline-investigation
Investigate AzDO pipeline failures beyond Helix — build errors, infra tooling crashes, validation test flakiness, artifact cascade failures. USE FOR: "why did the unified-build fail", "what's breaking the pipeline", "how often does this failure occur", "drill into build task logs", "1ES scan failure
test-arcade
Build the Arcade SDK from source, configure a local NuGet feed with the artifacts, and validate the build by running a test repository against the locally-built packages. Use when testing local Arcade changes against a consuming repo, validating Arcade SDK changes before merging, or verifying that a
Subagents (1)
ci-investigator
Orchestrate CI failure investigations for dotnet repositories. Routes to specialized skills based on failure type: ci-analysis for triage, helix-investigation for deep Helix log analysis, pipeline-investigation for build/infra failures, ci-crash-dump for crash dumps, known-issue-history for failure
Evidence-gated maintainability discipline in two layers. (1) A native plugin: four modes — /nihil:raze (root-authority, write-capable transformation of a repo you own; only secret-leak and catastrophic, unrecoverable commands are blocked) plus /nihil:review, /nihil:implement, /nihil:release with confidence scoring, scope control, and release gating — backed by five read-only review agents and PreToolUse/Stop hooks (a discipline aid, not a security boundary: heuristic command matching, fail-open; a secret / API-key brake is active in every mode). (2) A summonable pantheon of five first-principles dynamic workflows (/nihil orchestrator + /nihil-maat review, /nihil-odin research, /nihil-shiva deletion, /nihil-athena restructure), installed into .claude/workflows/ via /nihil:summon.
Code-elegance pipeline: 4 scouts, 2 judges, planner, verifier, and a gated implementer, plus a standalone code-simplifier for single-pass diff cleanups. Persistent state with stage gates.
Mutation-minded, behavior-first test quality. 4 agents (architecture reviewer, senior tester judge, expressive verifier improver, branch coverage implementer) + 4 skills. Coverage is a floor; kill power is the signal.
Dependency lifecycle: /derot audits comment/doc/CI/version/dependency rot and proposes fixes; /depmigrate migrates packages to their new APIs from upstream releases/tags — refutation-gated.
Statically analyze a local JS/Electron app you're authorized to study, with file+line evidence, and build an original reimplementation of what you find. Experimental. Phase 1: JS/Electron static analysis. Phase 2: native ELF/PE/Mach-O container inspection. Phase 3: .NET assembly metadata. Phase 4: EVM bytecode inventory. Phase 5: CUDA fatbin, cubin and PTX inventory. Parses, never executes. Dynamic analysis is a future phase, not yet implemented.
Agent skills for Azure SQL Developer, the Azure SQL Database engine running locally in a container. Teaches your agent to run the engine, connect, migrate, scaffold, build RAG, wire CI, and go local-to-cloud, using the real Private Preview image instead of the SQL Server image.
Skills for building apps with the AG-UI .NET SDK: streaming chat (stateless vs hosted agents), server tools, client tools, human-in-the-loop (approvals & interrupts), shared state, multimodal messages, reasoning traces, protobuf transport, and troubleshooting.
Write, run, and debug Ginkgo/Gomega test suites in Go: the tree-construction mental model, the full node and decorator surface, tables and generated specs, parallelism, filtering, timeouts and async, CI configuration, and JSON-first failure diagnosis.
13 skills
onsi/ginkgo 9,077
Maintain dotnet-dnceng?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.