codenavi

Navigate unknown codebases and record findings in a persistent .notebook/ knowledge base.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/jemluz/evervalue-station --skill codenavi-jemluz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codenavi
Source: https://github.com/jemluz/evervalue-station/tree/main/.cursor/skills/codenavi
Command: npx skills add https://github.com/jemluz/evervalue-station --skill codenavi-jemluz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often navigate large, unfamiliar codebases and accumulate scattered notes. CodeNavi provides a disciplined approach to discovery, documentation, and knowledge retention in a persistent notebook, reducing guesswork.

Core Features & Use Cases

  • Investigates codebases methodically and records findings in the .notebook/ knowledge base.
  • Summons available skills and MCPs when guidance is needed to solve complex tasks.
  • Supports bug fixes, feature work, refactoring, and flow investigations with surgical precision.

Quick Start

Begin by identifying the entrypoint of the problem area, document discoveries in .notebook/, and summon other skills or MCPs when guidance is needed.

Frequently Asked Questions about codenavi

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

FAQPage Schema
How do I navigate an unknown codebase to find the source of a bug?

To navigate an unknown codebase for debugging, you methodically investigate the problem area starting from its entrypoint and record exact findings in a persistent `.notebook/` knowledge base to eliminate guesswork. This approach ensures actionable intelligence is retained for complex bug fixes.

What is the best way to document findings when refactoring unfamiliar code?

The best way to document findings when refactoring code is to extract actionable intelligence into a persistent `.notebook/` directory, providing a disciplined approach to discovery and knowledge retention across diverse architectures.

How do I extract actionable intelligence from a codebase without guessing?

You extract actionable intelligence by navigating codebases methodically and refraining from guessing when information is missing, instead recording exact discoveries and summoning allied skills or MCPs when guidance is needed.

Does this codebase navigation approach work across diverse programming languages?

Yes, this codebase navigation approach applies directly to debugging, feature implementation, and refactoring across diverse languages and architectures, using a persistent notebook to retain knowledge regardless of the underlying tech stack.

When should I summon allied skills or MCPs during codebase investigation?

You should summon allied skills and MCPs during codebase investigation when guidance is needed to solve complex tasks, allowing you to maintain surgical precision while relying on exact findings rather than assumptions.