gabb-code-navigation

Teaches when to use gabb_structure for efficient file exploration.Use gabb_structure before reading large files in supported languages.

⭐2stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill provides advanced code navigation and exploration capabilities, enabling users to efficiently locate symbols and preview file structures across multiple programming languages. By utilizing specialized tools for symbol searching and layout mapping, it streamlines the process of understanding complex codebases, reduces token overhead when handling large files, and improves the precision of code-related tasks in AI-assisted development.

Use Cases

  • Case 1: Quickly locating specific function, class, or method definitions across a large workspace without manual searching.
  • Case 2: Previewing the structural layout of large source files (>100 lines) to identify relevant logic blocks before performing targeted reads.
  • Case 3: Navigating unfamiliar codebases in supported languages like Rust, Go, Python, and C++ by mapping out key types and symbols.
  • Case 4: Optimizing context window usage and reducing token costs by avoiding full-file reads when only specific sections are required for a task.
namegabb-code-navigation
description|
allowed-toolsmcp__gabb__gabb_structure, mcp__gabb__gabb_symbol, Edit, Write, Bash, Read, Glob

Gabb Code Navigation

Search Strategy Decision Flow

When you need to find code, follow this order:

  1. Task names specific file/function? → Read directly (skip exploration)
  2. Looking for a code construct by name? → gabb_symbol
  3. Looking for text content (strings, error messages)? → Grep
  4. Need to understand file layout? → gabb_structure

Search for symbols (functions, classes, methods) by name across the workspace.

When to use:

  • Task mentions a function/class/method name to find or fix
  • You need to find where something is defined
  • Grep would return too many false positives

Example:

gabb_symbol name="update_proxy_model_permissions"
→ function update_proxy_model_permissions [prod] migrations/0011_update_proxy_permissions.py:5:1

Use Grep instead when:

  • Searching for error messages or string literals
  • Looking for text patterns, not code identifiers

gabb_structure - File Layout Preview

First: Assess if exploration is needed (see MCP instructions). For trivial tasks with obvious targets, go directly to the file.

If exploring: Before reading large or unfamiliar code files, consider using gabb_structure to preview the layout. This saves tokens when you only need part of a large file.

Recommended for:

  • Large files (>100 lines) where you only need part
  • Unfamiliar codebases where you're exploring
  • Files you'll read multiple times

Skip when:

  • You already know exactly what you're looking for
  • The file is likely small (<100 lines)
  • You can answer from existing context
  • Files you've already seen structure for in this conversation
  • You're searching for string literals, regex patterns, or error messages (gabb_structure shows symbols, not strings—use Grep directly)

Supported Languages

Language Extensions
Python .py, .pyi
TypeScript .ts, .tsx
Rust .rs
Go .go
Kotlin .kt, .kts
C++ .cpp, .cc, .cxx, .hpp, .hh

Usage Patterns

gabb_symbol name="MyClass"
→ class MyClass [prod] src/models.py:45:1

File Structure Preview

1. gabb_structure file="src/large_file.rs"
   → Returns symbol names, kinds, line numbers (NO source code)

2. Read file_path="src/large_file.rs" offset=150 limit=50
   → Read only the section you need

What gabb_structure Output Looks Like

/path/to/file.rs:450
Summary: 15 functions, 3 structs | 450 lines
Key types: MyStruct (10 methods)

MyStruct st 10
 new fn 12
 process fn 17
helper fn 30
main fn 50

The output shows:

  • File path and line count
  • Summary stats (function count, struct count, line count)
  • Key types with method counts
  • Compact symbol tree: name kind_abbrev line with single-space indent for children