Use this skill to research $ARGUMENTS across all available repositories when the question is about impact analysis, consumers, producers, compatibility risk, migration scope, rollout planning, or cross-repo ownership.

Use cases for blast-radius analysis

Find consumers before changing a contract. Given an endpoint, RPC, topic, event, protobuf, schema, enum, table, config key, or shared type, locate repos that publish, consume, validate, transform, or test it.
Scope API and behavior changes. Identify services, clients, SDKs, generated code, docs, tests, and compatibility layers that depend on the current behavior.
Plan migrations and deprecations. Find remaining users of old flags, versions, endpoints, event names, schemas, or dependency APIs before removal.
Trace ownership across systems. Locate the owning repo, adjacent services, deployment config, runbooks, and callers when a request mentions an unfamiliar system.
Estimate rollout risk. Search for feature flag wiring, config defaults, environment overrides, CI workflows, dashboards, or alerts that may need coordinated changes.
Find copied logic and duplicate implementations. Search for similar validation, parsing, retry, auth, serialization, pagination, or error-handling code that might need the same fix.
Audit tests and safety nets. Locate unit, integration, contract, fixture, golden-file, and end-to-end tests that cover the changed behavior.
Correlate incidents or bugs across repos. Find shared error strings, log messages, metrics, spans, alerts, or fallback paths that reveal affected services.
Prepare stakeholder notes. Identify repos searched, concrete matches, owners, likely impacted surfaces, and unknowns that need human confirmation.

Workflow

Gather possible dependencies, make a discovery about the current project how it can be consumed
Read the project's curated repo list first. Each project may pin a hand-maintained list of external repositories in its agent instruction file. Read it before anything else and treat it as the primary source of candidate repos. Look in the current project, in this order, and use the first one that contains the list section: