codenavi

Explore unknown codebases and record findings in a .notebook knowledge base.

Updated Mar 29, 2026

Search Tags:#planning #documentation #codebase #mcp #investigate #notebook

Ready to run

npx skills add https://github.com/oiagorodrigues/qcontabil --skill codenavi-oiagorodrigues

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: codenavi
Source: https://github.com/oiagorodrigues/qcontabil/tree/main/.cursor/skills/codenavi
Command: npx skills add https://github.com/oiagorodrigues/qcontabil --skill codenavi-oiagorodrigues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Navigating unfamiliar codebases is error-prone and time-consuming. This Skill provides a methodical, risk-aware approach that uncovers dependencies, entry points, and data flow while recording insights in a reusable .notebook/ knowledge base.

Core Features & Use Cases

Methodical exploration of unknown projects to map structure, flows, and hotspots.
Persistent notebook integration that stores discoveries and references for future sessions.
Summons allies (other skills, MCPs, and docs) when clarifications are needed or when authoritative guidance is available.
Trigger-driven workflow for tasks like bug fixes, feature work, refactors, and investigation of unfamiliar flows.

Quick Start

Describe your codebase and your objective, and I will guide you through a mission cycle to explore, document, and understand the project.

Frequently Asked Questions about codenavi

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

FAQPage Schema

How do I navigate an unfamiliar codebase without breaking existing functionality?▼

To navigate an unfamiliar codebase safely, apply a methodical, surgical approach that maps dependencies, entry points, and data flow while verifying findings against source documentation to prevent errors during debugging or refactoring.

What is the best way to document codebase investigations for future sessions?▼

Documenting codebase investigations is best handled by recording discoveries and references in a persistent .notebook knowledge base, generating concise notes and actionable context that persist for future tasks.

Can I use MCPs and external docs to investigate unknown project flows?▼

Yes, you can summon MCPs and external docs as allies when investigating unknown project flows, ensuring clarifications are validated and authoritative guidance is applied directly to your feature work or debugging.

How do I start mapping project structure and hotspots in an unknown codebase?▼

Start mapping project structure and hotspots by describing your codebase and objective to trigger an exploration mission cycle, which systematically uncovers structural flows and records insights in your project notebook.

Does this approach work for both refactoring and debugging unfamiliar code?▼

Yes, this trigger-driven workflow supports refactoring and debugging unfamiliar code by applying a risk-aware approach that maps data flow and dependencies, ensuring changes are grounded in verified source documentation.