codebase-navigator

Map code symbols, API endpoints, and data flows across a monorepo.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/dankofly/Swing_B2B --skill codebase-navigator-dankofly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-navigator
Source: https://github.com/dankofly/Swing_B2B/tree/main/.claude/skills/codebase-navigator
Command: npx skills add https://github.com/dankofly/Swing_B2B --skill codebase-navigator-dankofly

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rg, ack, grep, git, tree, sed, find, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill eliminates the time-consuming manual process of locating symbols, components, API endpoints, and tracing data or call flows across a multi-service repository so engineers can quickly understand and navigate the codebase.

Core Features & Use Cases

  • Fast repository search: Uses ripgrep/ack/grep with portable wrappers to find functions, classes, types, components, and API routes across frontend and backend directories.
  • Trace flows end-to-end: Scripts to trace API request handling, service-level calls, schema definitions, and frontend usages to map data and control flow.
  • Project orientation: Provides architecture pointers and document references for backend (FastAPI) and frontend (Next.js) entry points to speed onboarding and debugging.

Quick Start

Find the FastAPI route handler for /api/v1/resumes, list the service functions it calls, and show where the frontend calls that API.

Frequently Asked Questions about codebase-navigator

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

FAQPage Schema
How do I trace API flows across a FastAPI and Next.js monorepo?

To trace API flows across a FastAPI and Next.js monorepo, this Skill maps backend route handlers, service-level calls, and frontend API usages end-to-end. It uses ripgrep and portable shell scripts to locate symbols and connect data flows across directories.

What is the best way to search for components and API endpoints in a full-stack codebase?

Searching for components and API endpoints in a full-stack codebase is done by executing portable ripgrep, ack, and grep wrappers. These scripts locate functions, classes, types, and routes across both Python backend and Next.js frontend directories to accelerate code discovery.

Do I need ripgrep installed to trace code symbols and data flows?

Yes, you need ripgrep installed to trace code symbols and data flows, along with a POSIX shell environment and access to repository files. The Skill's scripts also leverage dependencies like ack, grep, git, tree, sed, and find to perform code searches.

Can I use this to find where a specific schema is defined and used in my Python backend?

You can use this to find where a specific schema is defined and used in your Python backend by running the included trace scripts. The scripts audit schema definitions and map their usage throughout the FastAPI services to accelerate debugging.

How does codebase navigation work for understanding project architecture without reading every file?

Codebase navigation works by providing architecture pointers and document references for FastAPI and Next.js entry points. It instantly maps code symbols, API endpoints, and data flows so engineers can understand project architecture and orient themselves without reading every file.

What are the limitations of using ripgrep and grep for tracing code in a monorepo?

Using ripgrep and grep for tracing code in a monorepo requires a POSIX shell environment and specific text search dependencies to function properly. It focuses on static symbol and route matching rather than runtime execution tracing, so dynamic data flows may not be fully captured.