LeIndex-Code: Token-Efficient Code Analysis

VerifiedSafe

LeIndex-Code provides token-efficient code analysis via a 5-layer stack (AST, Call Graph, CFG, DFG, PDG), achieving 82% token savings in balanced mode with full semantic completeness for LLMs. It helps when you need to generate, refactor, or understand code while minimizing token usage in AI-assisted workflows.

Sby Skills Guide Bot
DevelopmentIntermediate
506/2/2026
Claude CodeCursorWindsurfCopilotCodex
#code-analysis#token-efficient#call-graph#semantic-search

Recommended for

Our review

LeIndex-Code provides token-efficient code analysis using a 5-layer stack (AST, Call Graph, CFG, DFG, PDG) to reduce token usage by up to 82% while preserving semantic completeness for LLM-assisted coding.

Strengths

  • Significant token savings (82% in balanced mode) without losing semantic information needed for code generation.
  • Multi-layer analysis (AST, call graph, control flow, data flow, program dependence) for deep code understanding.
  • Built-in semantic search for finding relevant code across a project.
  • Provides actionable LLM context with balanced mode while ultra mode for exploration.

Limitations

  • Ultra mode sacrifices significant semantic detail, not suitable for code generation.
  • Requires Python dependency (maestro.leindex) and may not be available in all environments.
  • The 82% savings is specific to balanced mode; savings may vary depending on codebase.
When to use it

Use LeIndex-Code when you need to provide an LLM with a condensed yet semantically complete view of your codebase for refactoring, debugging, or generating new code.

When not to use it

Avoid LeIndex-Code when you need full, uncompromised code context or when the codebase is very small where token savings are negligible.

Security analysis

Safe
Quality score90/100

The skill is a documentation reference for a Python library. It contains no destructive commands, data exfiltration instructions, or safety bypasses. The allowed-tools: [Bash] is metadata, but the skill itself does not instruct any bash execution beyond Python imports.

No concerns found

Examples

Token-efficient code context extraction
Extract token-efficient context for refactoring: use LeIndex-Code's ContextExtractor in balanced mode on the file 'src/api.py'.
Semantic search across project
Run semantic search for 'authentication' in '/path/to/project' using LeIndex-Code's semantic_search function.
Call graph analysis
Analyze the call graph of function 'analyze_file' in 'src/analyzer.py' using LeIndex-Code's CallGraphAnalyzer.

name: leindex-code description: Token-efficient code analysis via 5-layer stack (AST, Call Graph, CFG, DFG, PDG). 82% savings (balanced mode) with semantic completeness. allowed-tools: [Bash] keywords: [debug, refactor, understand, complexity, "call graph", "data flow", "what calls", "how complex", search, explore, analyze, dead code, architecture, imports]

LeIndex-Code: Complete Reference

Token-efficient code analysis with 82% token savings (balanced mode) while preserving semantic completeness for LLM usage.

Quick Reference

| Task | Command | |------|---------| | Context extraction | from maestro.leindex import ContextExtractor | | Semantic search | from maestro.leindex import semantic_search | | AST analysis | from maestro.leindex import ASTAnalyzer | | Call graph | from maestro.leindex import CallGraphAnalyzer |


Modes

Balanced Mode (Default) - 82% savings, LLM Actionable

Use for: Code generation, refactoring, implementation

from maestro.leindex import ContextExtractor

extractor = ContextExtractor(mode='balanced')  # Default
result = extractor.extract_for_file('src/api.py')

print(f"Savings: {result.savings_percent:.1f}%")
print(result.context.to_llm_string())

# Output includes:
# L119: analyze_file(file_path: str, include_call...) -> ContextExtractionResult
# L136: semantic_search(query: str, project_path..., limit: int)

Ultra Mode - 98% savings, Exploration Only

Use for: Code exploration, search, impact analysis

extractor = ContextExtractor(mode='ultra')
result = extractor.extract_for_file('src/api.py')

# Output:
# fn:analyze_file build_semantic_index get_token_savings
# (No signatures, NOT actionable for code generation)

Token Efficiency Comparison

| Mode | Savings | Semantic Quality | LLM Actionable | Use Case | |------|---------|------------------|----------------|----------| | Raw | 0% | Complete | ✓ Yes | Full file | | Balanced | 82% | High | ✓ Yes | Code generation | | Ultra | 98% | Low | ❌ No | Exploration only |

Key Insight: Balanced mode at 82% savings is the OPTIMAL balance for LLM-assisted coding. Ultra mode sacrifices too much semantic information (no signatures, no line numbers, no types) for LLM to accurately use the code.


Python API

from maestro.leindex import (
    # 5-layer analyzers
    ASTAnalyzer,
    CallGraphAnalyzer,
    CFGAnalyzer,
    DFGAnalyzer,
    SlicingAnalyzer,

    # Context extraction
    ContextExtractor,
    get_relevant_context,
    get_context_for_prompt,

    # Semantic search
    SemanticIndex,
    semantic_search,
    build_semantic_index,

    # Memory integration
    LeIndexMemoryBridge,
    get_leindex_memory_bridge,
)

# Example: Get token-efficient context (balanced mode)
extractor = ContextExtractor(mode='balanced')
result = extractor.extract_for_file('maestro/leindex/__init__.py')

print(f"Savings: {result.savings_percent:.1f}%")
print(f"Quality: {result.get_quality_report()}")

# Example: Semantic search
results = semantic_search("authentication functions", "/path/to/project")
for entity, score in results:
    print(f"{entity.name} in {entity.file} (score: {score:.2f})")
Related skills