Перевод: оболочка страницы на русском; тело навыка (SKILL.md) пока на английском — это исходные инструкции агента.

Codebase Navigate

Find symbols via project index CLI, not grep alone.

Метаданные навыка

Источник	Встроенный (установлен по умолчанию)
Путь	skills/software-development/codebase-navigate
Версия	1.0.0
Автор	VibeOS
Лицензия	MIT
Платформы	linux, macos
Теги	project, index, symbols, navigate, codebase
Связанные навыки	project-kanban-worktrees, git-local-workflow

Справка: полный SKILL.md

к сведению

Ниже полное определение навыка, которое VibeOS загружает при активации. Это инструкции, которые видит агент.

Codebase Navigate Skill

Use the project symbol index to jump to definitions by name before broad file walks. Index is CLI-only (no new model tools) — drive it with terminal.

Do not invent paths; query the index, then open hits with read_file.

When to Use

• User asks where a class/function/type lives in a large repo
• Kanban worker cwd is under .worktrees/<task> (scoped index)
• Before search_files / recursive greps for a known symbol name

Prerequisites

• Repo root or worktree with sources
• Optional pack: vibeos pack apply project-intelligence --apply

How to Run

1. Build or refresh the index (worktree-aware when cwd is under .worktrees/):

vibeos project index build
vibeos project index status

2. Query by substring of the symbol name:

vibeos project index query Widget
vibeos project index query find_widget --limit 20

3. Open the top hit with read_file at the reported path:line.

4. If status reports stale / missing:

vibeos project index build
vibeos doctor --project

Quick Reference

Goal	Command
Build index	vibeos project index build
Query symbol	vibeos project index query <name>
Status / stale	vibeos project index status
Doctor hints	vibeos doctor --project
Apply pack	vibeos pack apply project-intelligence --apply
Diagnostics cache	vibeos project diagnostics
Test/lint cmds	vibeos project commands

Procedure

1. Prefer vibeos project index query for named symbols.
2. Use search_files when the name is unknown or the index miss is expected (generated code, non-indexed languages).
3. In a kanban worktree, rebuild the scoped index after large pulls — status shows PROJ.index_stale when git HEAD moved.
4. Cite path:line from the index hit in replies and Board comments.

Pitfalls

• Index skips node_modules/, release/, and most dot-dirs — do not expect vendored symbols.
• Unregistered checkouts use local-<sha> ids; worktrees nest under $VIBEOS_HOME/projects/<id>/worktrees/<task>/index/.
• Do not add a core navigate tool — stay on CLI + terminal.

Verification

vibeos project index status
vibeos project index query <known_symbol>
vibeos doctor --project