메뉴
Find symbol definitions, trace call sites, and discover related files using Brokk's search_symbols, get_symbol_locations, scan_usages, and most_relevant_files tools.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | brokk-code-navigation |
| description | Find symbol definitions, trace call sites, and discover related files using Brokk's search_symbols, get_symbol_locations, scan_usages, and most_relevant_files tools. |
Use these Brokk MCP tools when you need to find where things are defined, who uses them, or which files in the project are related to a starting set.
| Tool | Purpose |
|---|---|
search_symbols | Find class, method, field, or module definitions by name (case-insensitive regex over fully-qualified names) |
get_symbol_locations | Get file + line range for known symbol names |
scan_usages | Find references, call sites, and related tests for known fully qualified symbols |
get_symbol_ancestors | Get the ancestor class chain (nearest parent first) for known classes |
most_relevant_files | Rank project files most related to a set of seed files (uses git history co-change and import graph) |
search_symbols takes an array of patterns. Patterns are case-insensitive
regexes matched against fully-qualified names, so a substring like
parseRequest matches com.example.http.ParseRequestHandler.parseRequest.include_tests: true to include matches from detected test files;
the default excludes tests.get_symbol_locations accepts both fully-qualified and short symbol names
and returns the first matching definition's file and line range. Use the
optional kind_filter (class, function, field, module, or any)
to disambiguate.scan_usages. It requires fully
qualified names, so run search_symbols first if you only have a partial
name. Static analysis may include false positives; unresolved symbols are
reported with structured reasons.most_relevant_files is the fastest way to expand from a known file
into adjacent code worth reading -- pass the file you are starting from
as a seed_file_paths entry and review the ranked results.Read implementation details and file structure using Brokk's get_symbol_sources, get_summaries, list_symbols, and get_file_contents tools.
File discovery and code search using Brokk's search_symbols, search_file_contents, find_files_containing, and find_filenames tools.
Explore change history using Brokk's search_git_commit_messages, get_git_log, get_commit_diff, and analyze_git_hotspots tools, with Bash git/gh for blame and GitHub lookups.
Guided end-to-end issue resolution workflow: select a GitHub issue, diagnose the codebase, plan changes, implement in an isolated branch, review with specialist agents, and open a pull request.
Interactive guided code review: gather changes, run parallel specialist agents, then walk through findings one-by-one with code context, triage, and an overall summary.
Deep adversarial review of pull request changes covering security, code duplication, intent verification, infrastructure, and architecture using Brokk code intelligence tools and parallel specialist agents.