discover

Maps repository structure, API surfaces, and governance rules through read-only exploration.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ZaxbyHub/ragappv3 --skill discover-zaxbyhub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discover
Source: https://github.com/ZaxbyHub/ragappv3/tree/main/.opencode/skills/discover
Command: npx skills add https://github.com/ZaxbyHub/ragappv3 --skill discover-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before modifying an unfamiliar codebase, engineers need a safe, structured way to understand its architecture, public APIs, complexity risks, and project governance rules without changing any files. ## Core Features & Use Cases - Explorer Delegation: Dispatches the swarm's explorer agent to survey the repository, with an optional second pass focused on hidden requirements, unstated assumptions, and scope risks. - API Surface Analysis: Runs symbols or batch_symbols on key files to map public interfaces, and complexity_hotspots to flag modules needing security review or full gates. - Governance Extraction: Locates project instruction files (project-instructions.md, CONTRIBUTING.md, INSTRUCTIONS.md) in priority order and writes extracted MUST/SHOULD rules to .swarm/context.md. - Use Case: When starting a feature in a large multi-module repo, run this protocol to produce a context file capturing architecture, risk hotspots, and mandatory contribution rules before writing any code. ## Quick Start Ask the architect agent to run MODE: DISCOVER on this repository to map its structure, risks, and governance rules.

Frequently Asked Questions about discover

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

FAQPage Schema
How do I explore an unfamiliar codebase before making changes?▼

Delegate a read-only survey to an explorer agent, then run symbols analysis on the key files it identifies to map public API surfaces. For complex tasks, run a second explorer pass focused on hidden requirements and scope risks.

How to extract coding rules from CONTRIBUTING or instruction files?▼

Search for governance files in priority order: project-instructions.md, docs/project-instructions.md, CONTRIBUTING.md, then INSTRUCTIONS.md. Read the first match and extract all MUST and SHOULD rules into a Project Governance section of the shared context file.

When should I use batch_symbols instead of single symbols calls?▼

Use batch_symbols when surveying multiple files or modules at once, since it is more efficient than sequential single-file symbols calls. Reserve single symbols calls for targeted inspection of one key file.

Does repository discovery modify any source files?▼

No, the discovery protocol is strictly read-only with respect to the repository. Its only write operation is appending extracted governance rules to the .swarm/context.md context file.

What happens if no project governance file exists?▼

The protocol skips governance extraction silently when no matching file is found. All other discovery steps, including explorer delegation and complexity hotspot analysis, proceed unchanged.