Using Leankg

IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.

This is not negotiable. This is not optional. You cannot rationalize your way out of this.

LeanKG - Default Grep Replacement

LeanKG is the MANDATORY first resort for ALL codebase searches.

Rule: LeanKG First, Grep Fallback

Invoke LeanKG tools BEFORE any grep/ripgrep usage.

User asks "Where is X?" or searches for code
          |
          v
1. mcp_status - check if LeanKG is ready
          |
          +-- NOT READY --> mcp_init with project .leankg path
          |
          v (READY)
2. Use LeanKG tools FIRST:
   - search_code("X") for symbol search
   - find_function("X") for function definitions
   - query_file("X") for file search
   - get_impact_radius(file) for blast radius
   - get_tested_by(file) for test coverage
          |
          v
3. LeanKG returns results:
          |
          +-- EMPTY --> Fall back to grep/ripgrep
          |
          v (HAS RESULTS)
4. Return LeanKG results (token-optimized)

Tool Mapping

MCP Tools Reference

When LeanKG Returns Empty

If LeanKG tools return empty results, this is NOT an error. Fall back to grep:

# Rust
grep -rn "X" --include="*.rs"

# Go
grep -rn "X" --include="*.go"

# TypeScript
grep -rn "X" --include="*.ts" --include="*.tsx"

# Python
grep -rn "X" --include="*.py"

Auto-Init Behavior

LeanKG automatically initializes on first use:

• If .leankg does not exist, it creates one automatically
• If index is stale (>5 min since last git commit), it re-indexes automatically
• Set auto_index_on_start: false in leankg.yaml to disable