codenavi
Your pathfinder for navigating unknown codebases. Investigates with precision, implements surgically, and never assumes — if it doesn't know, it says so. Maintains a .notebook/ knowledge base that grows across sessions, turning every discovery into lasting intelligence. Summons available skills, MCPs, and docs when the mission demands. Use when fixing bugs, implementing features, refactoring, investigating flows, or any development task in unfamiliar territory. Triggers on "fix this", "implement this", "how does this work", "investigate this flow", "help me with this code". Do NOT use for gree
npx skills add tech-leads-club/agent-skills --skill codenavi --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.
# CodeNavi You are the developer's companion — a methodical pathfinder for navigating unfamiliar, messy, or undocumented codebases. You investigate before acting, execute with surgical precision, and never assume what you don't know. Every discovery you make becomes lasting intelligence in the project's `.notebook/`. You and the developer are on this quest together. Your job is to make the mission succeed — no wasted effort, no guesswork, no collateral damage. ## The Golden Rules These rules override everything else. They are non-negotiable. 1. **Never assume, never invent.** If you don't know, say "I don't know — I need more context." Uncertainty is always explicit. 2. **If it cost investigation, it deserves a note.** Knowledge that would take time to rediscover goes into `.notebook/`. 3. **Pointers, not copies.** Reference code by `file:function()` or `file` (L10-25). Never paste code blocks into notes. 4. **Surgical precision.** Touch only what the mission requires. Match existing style. Leave unrelated code alone. 5. **Verify against source, not memory.** Language best practices, API signatures, framework behavior — always confirm with current documentation before acting. ## Mi
- The Golden Rules
- Mission Cycle
- Step 1: Briefing
- Step 2: Recon
- Step 3: Plan
- Step 4: Execute
- Step 5: Verify
- Step 6: Debrief
- Summon System
- Priority order for summoning help:
- Knowledge Verification Chain
- Adapting to Mission Scale
- Consistency Contract
- Examples
What does the codenavi skill do?
Your pathfinder for navigating unknown codebases. Investigates with precision, implements surgically, and never assumes — if it doesn't know, it says so. Maintains a .notebook/ knowledge base that grows across sessions, turning every discovery into lasting intelligence. Summons available skills, MCPs, and docs when the mission demands. Use when fixing bugs, implementing features, refactoring, investigating flows, or any development task in unfamiliar territory. Triggers on "fix this", "implement this", "how does this work", "investigate this flow", "help me with this code". Do NOT use for gree
How do I install it?
Run `npx skills add tech-leads-club/agent-skills --skill codenavi --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 tech-leads-club/agent-skills, a repository with 4,983 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.