Guide developers through briefing-to-verification cycles for undocumented codebases.
npx skills add https://github.com/barateza/dubweave --skill codenavi-barateza
Please help me install this Agent Skill. Skill: codenavi Source: https://github.com/barateza/dubweave/tree/main/.agent/skills/codenavi Command: npx skills add https://github.com/barateza/dubweave --skill codenavi-barateza
It helps you investigate unfamiliar, messy, or undocumented codebases methodically so you can implement changes safely without guessing.
.notebook/ knowledge base across sessions.Use the codenavi skill when you say what you want to change and include the task trigger phrase, for example: "Investigate why this bug happens and implement a minimal fix, then verify it no longer reproduces."
High-intent search queries and answers about installing and using this skill.
A structured codebase navigation workflow enforces a briefing-to-verification cycle, requiring you to consult project docs and verify existing patterns before implementing bug fixes, ensuring changes are grounded in observed evidence rather than assumptions.
The best way to implement features safely in an unfamiliar codebase is following a structured mission workflow of Recon, Plan, and Execute phases that mandates checking documentation and defining explicit success criteria before applying any code changes.
To ensure refactoring safety when navigating unknown code, follow a verification-first coding approach that requires creating plans with explicit success criteria and checking existing patterns before applying changes to the codebase.
Yes, you can persist code investigation findings across multiple sessions by recording discoveries into a growing `.notebook/` knowledge base, which maintains project intelligence for ongoing debugging and flow analysis tasks.
Yes, this codebase navigation method works for analyzing existing program flows by utilizing a structured Recon phase to gather evidence methodically, ensuring your flow analysis remains grounded in verified documentation and observed codebase behavior.
lossyrobDocument codebase component interactions with exact file:line references.
zinohomeEnforce test-first development with red-green-refactor cycles and automated test coverage.
SandroBeatzRun ESLint and TypeScript type checking on a codebase.
MatheusrlrNavigate unknown codebases and maintain persistent knowledge in `.notebook/`.