newrelic

Use when the user mentions a Dotty PR, dotty (package/dependency) updates, or asks to update the .NET agent compatibility docs / net-agent-compatibility-requirements after tested library version bumps.

Run the New Relic .NET agent integration tests locally. Use whenever you need to run, debug, or reproduce an integration test (host-run IntegrationTests, UnboundedIntegrationTests, or ContainerIntegrationTests), are verifying an agent/wrapper change end to end, or find yourself reaching for `dotnet test` against a test project in this repo. You run these from the CLI yourself -- secrets and infra are already in place. Covers the build-first prerequisite, picking the layer, the run command per layer, and the env gotchas behind confusing failures.

Mandatory unit-test and code-coverage rules for the .NET agent. Use when writing an implementation plan, writing or modifying unit tests, or adding/changing production code in the Core project or the NewRelic.Agent.Extensions project. Apply without being prompted by the user.

Build the New Relic .NET agent locally and validate that code changes compile. Use this whenever you are about to build the agent, need to confirm your edits compile, need to refresh the agent home directories (newrelichome_*) before running tests, or find yourself reaching for `dotnet build` / `msbuild` on any project in this repo. Always build the full solution from the CLI in Debug -- never a single project. Covers that command and the traps that waste time (building individual projects, Release config, building the profiler by hand, dragging preview SDKs into build tools).

Open an Angler PR that adds the latest .NET agent release to metric_names.txt. Use when the user asks to add a .NET agent version to Angler, update Angler for a new agent release, or "create the Angler PR" after a .NET agent release ships.

Application Performance Monitoring and transaction analysis. Use when investigating application errors, slow response times, throughput issues, or transaction-level problems.

Cloud FinOps cost analysis. Use when investigating cloud spend, cost anomalies, cost spikes, budget analysis, or any questions about AWS, Azure, GCP costs and billing. Requires a New Relic account with Cloud Cost Intelligence data ingested into the CloudCostV2Test table.

Kubernetes diagnosis and debugging using New Relic telemetry. Use when investigating pod crashes, CrashLoopBackOff, OOMKills, pod evictions, scheduling failures, container restarts, node pressure, HPA/scaling issues, service disruptions, or other Kubernetes workload problems. Requires a New Relic account with nri-kubernetes / kube-state-metrics data ingested.

Use this skill whenever the user wants to query, debug, monitor, or analyze anything in New Relic — including logs, metrics, traces, APM data, alerts, incidents, dashboards, or infrastructure. Triggers on phrases like "check New Relic", "query NRQL", "look at alerts", "analyze performance", "what's happening in production", "check error rate", "find slow transactions", "investigate incident", or any request to pull observability or monitoring data. Also triggers when the user mentions APM, distributed tracing, golden signals, Errors Inbox, or synthetic monitors. Always use this skill rather than guessing — it contains the tool list, NRQL syntax, and multi-step workflows needed to do it right.

Fixes a CVE in nrdot distributions by looking up the CVE details, finding the installed vulnerable version in the generated go.sum files, adding a Go module replace directive to all affected manifest.yaml files, then regenerating licenses and committing the fix.

Analyzes OpenTelemetry Collector component version bumps and compiles a markdown summary of relevant changes (breaking changes, deprecations, bug fixes) from the upstream CHANGELOG files. Only includes changes for components used in the nrdot releases repo. Outputs a formatted comment ready to paste into a GitHub PR.

Enter Builder mode — suspend the demo Prime Directive so the demo-engineering team can develop/maintain the app.