codenavi

Navigate unfamiliar codebases and document findings in a .notebook/ knowledge base.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Mercurykz/Barretao- --skill codenavi-mercurykz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codenavi
Source: https://github.com/Mercurykz/Barretao-/tree/main/.cursor/skills/codenavi
Command: npx skills add https://github.com/Mercurykz/Barretao- --skill codenavi-mercurykz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You are a methodical pathfinder for navigating unfamiliar codebases. You investigate before acting, document findings in a persistent .notebook/ knowledge base, and coordinate with MCPs and other skills to avoid guesswork.

Core Features & Use Cases

  • Maintains a growing .notebook/ knowledge base across sessions
  • Sums available skills, MCPs, and docs when the mission demands
  • Triggers on developer prompts like "fix this", "investigate this flow", or "how does this work"

Quick Start

Instruct the agent to map an unfamiliar module by outlining entry points, dependencies, and risks.

Frequently Asked Questions about codenavi

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

FAQPage Schema
How do I investigate an unfamiliar codebase before starting a refactoring task?

Codebase navigation works by applying methodical, evidence-based exploration triggered by developer prompts like 'fix this' or 'investigate this flow'. It maintains a growing .notebook/ knowledge base across sessions, documenting findings and referencing official docs or MCPs when needed.

How do I debug complex code flows in a large codebase without guessing?

To map an unfamiliar module, instruct the agent to outline its entry points, dependencies, and risks. This methodical pathfinding approach applies evidence-based exploration to document architectural findings in a .notebook/ knowledge base for persistent reference.

Can I maintain a persistent knowledge base when navigating code across multiple sessions?

Documenting findings during codebase exploration creates a persistent .notebook/ knowledge base that prevents knowledge loss across sessions. This evidence-based approach ensures methodical investigation of complex flows while coordinating with MCPs and other skills to avoid guesswork.

What is the best way to navigate complex execution flows during debugging?

Codebase navigation works by applying methodical, evidence-based exploration triggered by developer prompts like 'fix this' or 'investigate this flow'. It maintains a growing .notebook/ knowledge base across sessions, documenting findings and referencing official docs or MCPs when needed.

How do I map an unfamiliar module by outlining entry points and dependencies?

To map an unfamiliar module, instruct the agent to outline its entry points, dependencies, and risks. This methodical pathfinding approach applies evidence-based exploration to document architectural findings in a .notebook/ knowledge base for persistent reference.

Does codebase navigation work with MCPs and other skills for investigating complex flows?

Yes, codebase navigation coordinates with MCPs and other skills when investigating complex flows. This integration sums available skills, MCPs, and docs on demand, ensuring evidence-based exploration that avoids guesswork while documenting findings in a .notebook/ knowledge base.