org-search

Use this skill to research $ARGUMENTS across all available repositories, especially when the answer may live outside the current repo.

Use cases for cross repository search

• Find reusable components, libraries, or utilities. Before writing new code, check whether another repo already exposes a client, helper, or shared package that solves the problem.
• Locate prior art and reference implementations. Discover how other teams have already solved a similar design problem (e.g. retry logic, feature flag wiring, pagination, caching, auth middleware) so a new implementation can follow established patterns.
• Trace cross-service API consumers and producers. Given an endpoint, RPC, topic, or event name, find every repo that publishes or consumes it to understand blast radius before changing a contract.
• Find usages of a shared library, type, or symbol across the org. Useful for migrations, deprecations, and breaking-change planning — answer "who imports this?" when the symbol is defined in a shared package.
• Investigate unfamiliar systems and code ownership. When a request mentions a service, table, or feature you don't recognize, search the org to find the owning repo, its README, and entry points before asking a human.
• Audit security, compliance, or anti-pattern occurrences. Sweep all repos for risky patterns (hardcoded secrets shapes, deprecated crypto, banned dependencies, unsafe SQL) to scope remediation work.
• Discover configuration and infrastructure examples. Find how other services configure the same tool (CI workflows, Dockerfiles, Terraform modules, Helm charts, observability setup) to copy a known-good baseline.
• Cross-reference schemas, protos, and shared data models. Locate the canonical definition of a type or message and every repo that depends on it.
• Reproduce or correlate bugs across services. When a bug may stem from a shared dependency or duplicated logic, search the org for the same code path or error string.
• Onboarding and documentation lookup. Surface relevant docs, runbooks, and examples that live outside the current repo when the local codebase doesn't fully explain a workflow.

Workflow

1. Find candidate repositories first. Run the experimental repo discovery command before searching code: