richlander

Find evidence instead of guessing for .NET packages, platform libraries, local assemblies, APIs, dependencies, and version-to-version API changes.

Whole-assembly call-graph leverage ranking and performance triage for libraries (experimental).

Decide whether a change or upgrade is safe — API-surface diffs, behavioral diffs (allocations, exceptions), feature switches, and version resolution.

Judge whether code is sound and safe to call — its exception surface (throws, catches, exception types) and the unsafe operations in a method body.

Reconstruct a method or type locally as C# and IL — decompiled source, annotated source with hidden facts, raw IL, fidelity levels, and IL-offset lookup. Always local, no network.

Use for opt-in Deep Inspect run triage: test lane failures, census artifacts, pinned-subset drift, and routing findings into issues or tracker updates.

Run and interpret opt-in expensive validation lanes: full slow tests, IL round-trip sweep, corpus sensors, validity scans, and analysis census.

Map how code connects — implementors and subclasses, extension methods, dependency graphs, reverse callers, and ecosystem integrations. Many outputs are graph-shaped (add --mermaid).

The complete Markout coding-agent integration guide: installation, the required 3-part source-generation pattern (annotate, register on a partial MarkoutSerializerContext, serialize through it), the full attribute reference (including MarkoutLink, MarkoutValueMap, MarkoutSection.GroupBy, MarkoutMaxItems, MarkoutBoolFormat), every built-in shape type (Metric, Breakdown, Callout, TreeNode, Description, CodeSection), and formatter selection (Markdown, TSV, plain text, Spectre). Markout has NO reflection fallback, so a MarkoutSerializerContext is always required.

Experiment harness shell for the custom MCP delivery environment on the Markout task. Carries no inline grounding; curated package context is delivered only via the get_package_context MCP tool when the agent chooses to call it (gate under test = GROUNDING_GATE).

Experiment harness shell for the MCP delivery environment (ambiguous multi-package triage). Carries no inline grounding; package context for any referenced package is delivered only via the get_package_context / summarize_package_context MCP tools when the agent chooses to call them.

Experiment harness shell for the MCP delivery environment (multi-package triage). Carries no inline grounding; package context for any referenced package is delivered only via the get_package_context MCP tool when the agent chooses to call it.

Experiment harness shell that attaches the real upstream NuGet MCP server (NuGet.Mcp.Server). Carries no inline grounding; package context is delivered only via the server's get_package_context tool when the agent chooses to call it.

Experiment harness shell for the MCP delivery environment. Carries no inline grounding; package context is delivered only via the get_package_context MCP tool when the agent chooses to call it.

Experiment harness shell for the MCP delivery environment (resident-API probe). Carries no inline grounding; System.Text.Json context is delivered only via the get_package_context MCP tool when the agent chooses to call it.

Official System.CommandLine package README and getting-started documentation. System.CommandLine provides robust support for command-line parsing, invocation, and shell completions in .NET applications. Use when building or working with System.CommandLine command-line apps.

Stand up and run a Nightshift shift: start the Turnstile coordination daemon, author and register a plan (orders.json → a DAG of landable-PR "orders"), keep the ready set live, land merged orders to unblock their dependents, and drain or stop the shift. Use this when asked to set up, register, drive, or wind down a Nightshift backlog (the operator/coordinator side, not the worker side).

Build one Nightshift order into a set of commits on its branch: make the change within the order's declared file scope, keep the claim alive with `nightshift check` before every commit, and use the required commit trailers. You never push; you hand the branch back. Use this when a Nightshift worker dispatches you to build (or rework) a single order.

Review one Nightshift order's diff as an independent adversarial reviewer: work read-only in the prepared worktree at the exact head, report only high-confidence bugs with file:line — each classified blocking, non-blocking, or pre-existing — and hand your findings back to whoever dispatched you. Use this when a Nightshift worker dispatches you to review an order.

Operate as a Nightshift night-shift worker: claim one unit of work (an "order" = one landable PR) from the Turnstile coordination kernel and take it to a reviewed branch — building it and reviewing it (usually by spawning subagents), driving the adversarial gate to two clean, then handing it back. Use this whenever you are launched to work a Nightshift backlog, or told to "run nightshift", "take the next order", or "join the shift".

Answer .NET release lifecycle, timeline, patch, and CVE questions by driving the public `dotnet-release` CLI over the release-index graph.

Update per-distro package files in release-notes/<version>/distros/ documenting dependencies and .NET package availability for each Linux distribution.

Audit and update os-packages.json files in dotnet/core to ensure Linux distribution package names are correct. Verifies package names against upstream package repositories and fixes mismatches.

Audit and update supported-os.json files in dotnet/core to reflect current OS version support. Uses release-notes verify for automated checking against upstream lifecycle data.

Build, install, list, and remove .NET tools using dotnet-install.

Build, install, list, and remove .NET tools using dotnet-install.

Publishing and release workflow for dotnet-install. Version bumps, CI, NuGet publish, GitHub Releases.

Cross-tool workflow to reduce .NET heap allocations — static triage with dotnet-inspect, then confirm the win with BenchmarkDotNet or dotnet-trace/dotnet-counters before changing code. Use when chasing allocation hot spots on a hot path.

Find evidence for .NET packages, platform libraries, assemblies, APIs, dependencies, SourceLink/source, and API version diffs.

Source-generated .NET serializer that renders objects as Markdown (also ANSI terminal, plain text, pretty tables, TSV/JSONL). Use it when a CLI or tool needs structured, human- or agent-readable output instead of hand-built strings; it requires a generated MarkoutSerializerContext and Markout attributes (no reflection fallback).

Analyze music listening data across Last.fm, YouTube, and Discogs. Run queries to find listening stats, discover new artists, identify strange absences, track surging interests, and build playlists from cross-source analysis.

Markout serializer grounding (fixture). Use for Markout output questions.

Use dotnet-scope to diagnose .NET build errors. When a dotnet build fails, pipe the output to `dotnet-scope diagnose` to get enriched diagnostics with source context, documentation links, and suggestions for common errors like typos in method names.