メニュー
Post-processes dotnet-inspect@0.7.8 -- diff output into a categorised report (breaking / additive / newly-obsolete) with each finding cross-referenced to the MAF obsolete-API registry.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Detects new MAF releases, extracts breaking changes, and keeps the toolkit's registry/matrix/guide current. Pipeline: (1) deterministic data extraction via GitHub Actions + Python helpers + dotnet-inspect, opens a PR with raw data and TODOs on a per-version branch (never commits direct to main), (2) optionally, a maintainer manually runs a sibling workflow that opens a GitHub issue for GitHub Copilot Coding Agent to fill the TODOs, (3) Copilot opens a PR with the fills. This skill documents the whole loop end-to-end.
The fix-everything playbook for the maf-remediate loop: per-rule canonical fix + how to tell a real finding from a false positive (by confidence tier). Use when driving a codebase to a clean MAF health grade — triage heuristic findings before changing code.
Machine-readable registry of known CS0618 obsolete API warnings for MAF migrations. Each entry maps an obsolete method signature to its replacement, with the exact fix pattern. Prefer the MCP tool MafRegistryLookup (by ID) or MafApiSafety (by symbol) for one-shot queries; this skill is for understanding the registry schema and contributing new entries. Load this skill when cs0618-hunter has identified a CS0618 warning and you need the deterministic fix.
Maintainer runbook for keeping maf-autopilot current with new MAF releases. Use when a new MAF version has shipped and .maf-version is stale. Covers the full loop: pre-flight check → trigger watcher → monitor PR → fill TODOs → review → merge. Distinct from maf-release-watcher (which describes what the automation does internally); this skill tells YOU what to do as the operator.
Cross-framework migration map: Semantic Kernel (C#) → Microsoft Agent Framework. Load this skill when porting an SK app to MAF (NOT a MAF version bump). It is the smart index over docs/migration/from-semantic-kernel-to-maf.md — it tells you each SK construct's MAF target and its migration strategy (🌉 bridge / 🔁 rewrite / 🏗 re-architect), so you migrate construct-by-construct, side-by-side, non-destructively.
Validates fan-out / fan-in workflow topology — detects the silent fan-in starvation pattern (handlers returning void / non-generic Task that produce no downstream message). Canonical rules + procedure for what the compiler cannot catch and the build cannot surface.
| name | nuget-diff-analyzer |
| description | Post-processes dotnet-inspect@0.7.8 -- diff output into a categorised report (breaking / additive / newly-obsolete) with each finding cross-referenced to the MAF obsolete-API registry. |
⚡ Prefer the MCP tool. The
maf-autopilotMCP server exposesMafDiffPackage(packageId, oldVersion, newVersion)— it wrapsdotnet-inspect@0.7.8 -- diff, parses the markdown output into a structuredDiffParseResult(Breaking / Additive / NewlyObsolete lists), and cross-references each finding against the obsolete-API registry. The procedural walkthrough below is preserved for when you need to run the steps manually.
Raw dotnet-inspect diff output is markdown-pretty but unstructured — the LLM has to re-parse it on every call. The MCP tool does the parsing once and returns structured findings that downstream tools (best-practice reviewer, migration auditor) can consume directly.
# Step 1: emit the raw diff
dnx dotnet-inspect@0.7.8 -y --source https://api.nuget.org/v3/index.json -- diff \
--package Microsoft.Agents.AI@1.2.0..1.3.0 --source https://api.nuget.org/v3/index.json
# Step 2: read the output. It has the shape:
# # API Diff: <package>
# | Versions | **1.2.0** -> **1.3.0** |
# | Summary | N breaking, M additive across K types |
#
# ## Breaking Changes
# ### <Type>
# - Member '...' signature changed: `oldSig` -> `newSig`
# - Member '...' was removed
#
# ## Additive Changes
# ### <Type>
# - Type '...' was added
# - Member '...' was added
# Step 3: for each breaking change, look up the registry:
# MafApiSafety("<symbol-name>")
# or browse .github/skills/maf-obsolete-api-registry/registry.yaml
MafDiffPackage produces)| Category | Origin in diff output | Action |
|---|---|---|
| Breaking | ## Breaking Changes section | Add to migration plan; high risk |
| Additive | ## Additive Changes section | Inform future patterns; not urgent |
| NewlyObsolete | Any entry whose body contains [Obsolete...] | Inspect; likely a deprecation flag |
Use dotnet-inspect@0.7.8 or later. Earlier versions miss [Obsolete] at the overload level — see issue #316. The pinned dnx invocation in the manual fallback above already reflects this.