workspace-navigation

Locate repositories and reference files matching a pattern in multi-repo workspaces.

6|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/open-hax/opencode-skills --skill workspace-navigation-open-hax
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspace-navigation
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/workspace-navigation
Command: npx skills add https://github.com/open-hax/opencode-skills --skill workspace-navigation-open-hax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Locate the correct repository, file, and pattern quickly in a large, multi-repo workspace with many submodules.

Core Features & Use Cases

  • Repo discovery: Identify the most likely repository under common roots such as orgs/** or src/.
  • Pattern matching: Locate 1-2 reference files that match the requested pattern.
  • Safe edits: Confirm the expected edit location before making changes.

Quick Start

Provide the target feature or workflow description and I will locate the appropriate repo and file.

Frequently Asked Questions about workspace-navigation

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

FAQPage Schema
How do I locate the correct repository and file in a multi-repo workspace?

Locating the correct repository and file involves scanning common roots such as orgs/** and src/ to identify 1-2 reference files matching your requested pattern, verifying the exact path before editing.

What is the best way to find reference files matching a specific pattern across multiple submodules?

Finding reference files across submodules requires pattern matching against common workspace roots like orgs/**, narrowing down to 1-2 candidate files that match the requested codebase pattern for safe modification.

How do I navigate a large codebase to find where a specific feature is implemented?

Navigating a large codebase to find a feature implementation uses repo discovery to scan structural roots like src/, matching your feature description against reference files to return the exact file path for safe edits.

Can I verify an edit location before modifying files in a multi-repo workspace?

Yes, you can verify an edit location before modifying files by confirming the target path identified during the repository and pattern scanning process, ensuring safe modifications across the multi-repo workspace.

Does workspace navigation work for scanning multiple repositories under orgs or src directories?

Workspace navigation works for scanning multiple repositories by targeting common organizational roots like orgs/** and src/, effectively discovering the correct repo and narrowing down to the specific reference files.