12 个 · 按相关度排序
Capture MSBuild execution records as binary logs during .NET builds, tests, packaging, publishing, or restores. It explains unique filenames, PowerShell quoting, and file checks so logs remain available for later failure or performance analysis.
中文简介正在准备中。当前显示英语简介。
Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. USE FOR: adding /bl:{} 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+ / .NET 8 SDK+ for {} placeholder; PowerShell must quote the complete switch as '-bl:{}'. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake), analyzing an existing binlog (use binlog-failure-analysis instead), binlog MCP startup failures (use troubleshoot-binlog-mcp).
中文简介正在准备中。当前显示原文说明。
Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. Only activate in MSBuild/.NET build context. USE FOR: adding /bl:{} 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+ / .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). INVOKES: shell commands (dotnet build /bl:{}).
中文简介正在准备中。当前显示原文说明。
Analyze agent runs that fail before any work begins. Check iteration counts, tool use, logs, and outputs to identify startup failures, then direct investigation toward environment setup, input formatting, permissions, or resource limits.
中文简介正在准备中。当前显示英语简介。
Diagnose why the dotnet-msbuild binlog MCP server will not start or connect. Check the selected SDK, package sources, and launch logs, then identify a recovery that respects organizational policies and verify that the host discovers the server’s tools.
中文简介正在准备中。当前显示英语简介。
Diagnose MSBuild failures from an existing binary build log. Inspect errors, settings, project references, and execution details to explain failures that console output alone does not clarify, including failures across multiple projects.
中文简介正在准备中。当前显示英语简介。
Diagnose dotnet-msbuild binlog MCP startup failures. USE FOR: CONNECTION_CLOSED, binlog server won't connect, missing binlog tools, Microsoft.AITools.BinlogMcp not found, dnx launch errors. Checks workspace SDK, feeds, and source mapping without bypassing policy. DO NOT USE FOR: errors inside a binlog (use binlog-failure-analysis), capturing binlogs (use binlog-generation), unrelated MCP servers.
中文简介正在准备中。当前显示原文说明。
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), binlog MCP startup or connection failures (use troubleshoot-binlog-mcp), non-MSBuild build systems.
中文简介正在准备中。当前显示原文说明。
Test execution reference: framework detection (pytest/jest/vitest/go/cargo/junit) and correct run/coverage commands, plus failure-analysis steps. Use when running tests, analyzing test failures, or verifying coverage after code changes.
中文简介正在准备中。当前显示原文说明。
Diagnosis of why structural materials fail — ductile overload, brittle cleavage, fatigue, creep, stress-corrosion cracking, hydrogen embrittlement, and corrosion. Covers Griffith fracture mechanics, the ductile-to-brittle transition, the S-N and Paris fatigue frameworks, fractographic interpretation, and the J.E. Gordon view that strength, stiffness, and toughness are distinct properties that must be understood together to prevent collapse.
中文简介正在准备中。当前显示原文说明。
Analyze MSBuild binary logs to diagnose build failures. Only activate in MSBuild/.NET build context. 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. INVOKES: binlog MCP server tools (overview, errors, search, items, properties); falls back to dotnet msbuild binlog replay + grep/cat when the MCP is unavailable.
中文简介正在准备中。当前显示原文说明。
Investigates DAG incidents with a precise top event, timeline, competing hypotheses, barriers, propagation, and bounded recovery. NOT for automated root-cause classification, trace collection, or performance profiling.
中文简介正在准备中。当前显示原文说明。