doc-navigator
Efficiently navigate codebase documentation during Research phase. Use instead of Grep/Glob for finding architectural decisions, feature specs, and technical docs. Maps topics to doc locations for fast context retrieval. If codebase lacks documentation structure, provides patterns to establish one.
npx skills add majiayu000/claude-skill-registry --skill doc-navigator-georgekhananaev-claude-skills-vault-2 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Doc Navigator Navigate codebase documentation efficiently by checking known doc locations first, before resorting to grep/glob searches. ## When to Use - Finding architectural decisions (ADRs) - Locating feature specs or API docs - Researching codebase before implementation - Suggesting documentation structure for new projects - Alternative to grep/glob for doc discovery ## Quick Start 1. Check for docs directory at project root 2. Scan for common doc file patterns 3. If docs exist → map topics to locations 4. If no docs → suggest documentation structure (see `references/doc-patterns.md`) ## Common Documentation Locations Check these locations in order: ``` project-root/ ├── docs/ # Primary documentation │ ├── architecture/ # System design, ADRs │ ├── features/ # Feature specs │ ├── api/ # API documentation │ └── guides/ # How-to guides ├── .github/ # GitHub-specific docs │ └── docs/ ├── README.md # Project overview ├── ARCHITECTURE.md # High-level architecture ├── CONTRIBUTING.md # Contribution guidelines └── doc/ or documentation/ # Alternative doc folders ``` ## Topic-to-Location Mapping | Looking for... | Check first | |----------------|-------------| | Project overview | `RE
- When to Use
- Quick Start
- Common Documentation Locations
- Topic-to-Location Mapping
- Discovery Workflow
- Automated Discovery
- When Docs Don't Exist
- Finding Decisions Without ADRs
- Integration with Research Phase
python3 scripts/scan_docs.py [project-path]
What does the doc-navigator skill do?
Efficiently navigate codebase documentation during Research phase. Use instead of Grep/Glob for finding architectural decisions, feature specs, and technical docs. Maps topics to doc locations for fast context retrieval. If codebase lacks documentation structure, provides patterns to establish one.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill doc-navigator-georgekhananaev-claude-skills-vault-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.