Explore Codebase

Other Community

Skill notes

Steps

Run list_graph_stats to see overall codebase metrics. Run get_architecture_overview for high-level community structure. Use list_communities to find major modules, then get_community for details. Use semantic_search_nodes to find specific functions or classes. Use query_graph with patterns like callers_of, callees_of, imports_of to trace relationships.

Tips

Start broad (stats, architecture) then narrow down to specific areas. Use children_of on a file to see all its functions and classes. Use find_large_functions to 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.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
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 explicit requirements detected
Detected file/system behavior
  • Read-only
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

## Explore Codebase

Use the code-review-graph MCP tools to explore and understand the codebase.

### Steps

1. Run `list_graph_stats` to see overall codebase metrics.
2. Run `get_architecture_overview` for high-level community structure.
3. Use `list_communities` to find major modules, then `get_community` for details.
4. Use `semantic_search_nodes` to find specific functions or classes.
5. Use `query_graph` with patterns like `callers_of`, `callees_of`, `imports_of` to trace relationships.
6. Use `list_flows` and `get_flow` to understand execution paths.

### Tips

- Start broad (stats, architecture) then narrow down to specific areas.
- Use `children_of` on a file to see all its functions and classes.
- Use `find_large_functions` to 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.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.