Explore Codebase
- Repo stars 17,985
- Author updated Live
- Author repo code-review-graph
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tirth8205 · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Shell exec
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: Explore Codebase
description: Navigate and understand codebase structure using the knowledge graph Use the code-review-graph M…
category: other
runtime: no special runtime
---
# Explore Codebase output preview
## PART A: Task fit
- Use case: Navigate and understand codebase structure using the knowledge graph Use the code-review-graph MCP tools to explore and understand the codebase. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Explore Codebase / Steps / Tips” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Navigate and understand codebase structure using the knowledge graph Use the code-review-graph MCP tools to explore and understand the codebase. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Explore Codebase / Steps / Tips” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, run shell commands, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Explore Codebase / Steps / Tips”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: Explore Codebase
description: Navigate and understand codebase structure using the knowledge graph Use the code-review-graph M…
category: other
source: tirth8205/code-review-graph
---
# Explore Codebase
## When to use
- Navigate and understand codebase structure using the knowledge graph Use the code-review-graph MCP tools to explore an…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Explore Codebase / Steps / Tips” and keep inference separate from source facts.
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "Explore Codebase" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Explore Codebase / Steps / Tips
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, run shell commands, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Explore Codebase
Use the code-review-graph MCP tools to explore and understand the codebase.
Steps
- Run
list_graph_statsto see overall codebase metrics. - Run
get_architecture_overviewfor high-level community structure. - Use
list_communitiesto find major modules, thenget_communityfor details. - Use
semantic_search_nodesto find specific functions or classes. - Use
query_graphwith patterns likecallers_of,callees_of,imports_ofto trace relationships. - Use
list_flowsandget_flowto understand execution paths.
Tips
- Start broad (stats, architecture) then narrow down to specific areas.
- Use
children_ofon a file to see all its functions and classes. - Use
find_large_functionsto identify complex code.
Token Efficiency Rules
- ALWAYS start with
get_minimal_context(task="<your task>")before any other graph tool. - Use
detail_level="minimal"on all calls. Only escalate to "standard" when minimal is insufficient. - Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review