repo-navigator

Locate cross-repo CRD controllers and RPC topology using architectural index maps and LSP navigation.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/COLDTURNIP/longhorn-workspace --skill repo-navigator-coldturnip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-navigator
Source: https://github.com/COLDTURNIP/longhorn-workspace/tree/main/.opencode/skills/repo-navigator
Command: npx skills add https://github.com/COLDTURNIP/longhorn-workspace --skill repo-navigator-coldturnip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers quickly locate logic that spans multiple Longhorn repositories by leveraging pre-generated architectural indices and LSP-based navigation, reducing search time and cognitive load.

Core Features & Use Cases

  • Architectural index-guided navigation: uses crd-interaction.json and rpc-topology.json to anchor search space across repositories.
  • LSP-enabled discovery: after locating the anchor file, uses language-server capabilities to jump to definitions and references.
  • Cross-repo use cases: identify CRD controllers or RPC service topology across the Longhorn codebase and related repos.

Quick Start

Use the repo-navigator to locate the CRD controller for Volume: bash .opencode/skills/repo-navigator/repo_navigator.sh --crd Volume Find the topology for an RPC service: bash .opencode/skills/repo-navigator/repo_navigator.sh --rpc InstanceServiceClient

Frequently Asked Questions about repo-navigator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I navigate cross-repo logic across multiple Longhorn repositories?

To navigate cross-repo logic, use architectural indices like crd-interaction.json and rpc-topology.json to anchor the search space, then apply LSP-based navigation to jump to definitions and references within those anchor files.

What is the best way to find a CRD controller for a specific resource in Longhorn?

The best way to find a CRD controller is to run the repo-navigator script with the --crd flag, which consults the architectural index to quickly locate the relevant controller logic across the codebase.

How do I trace RPC service topology across different repositories?

Trace RPC service topology by running the navigator script with the --rpc flag, using the rpc-topology.json map to identify the service topology and locate the relevant RPC client logic across repositories.

Can I use language server protocol capabilities to find definitions after locating an anchor file?

Yes, you can use language server protocol capabilities to find definitions and references. The tool first uses architectural indices to locate the anchor file, then applies LSP-enabled discovery for precise navigation.

Do I need pre-generated architectural indices to search for logic spanning multiple repositories?

Yes, pre-generated architectural indices are required. The tool relies on existing crd-interaction.json and rpc-topology.json files to anchor the search space before applying LSP-based navigation to locate cross-repo logic.