using-leankg

name	using-leankg
description	Use for ANY code search, navigation, or finding code logic - "where is X", "find logic Y", "how does Z work", impact analysis, dependencies. LeanKG is MANDATORY first. Use when this capability is needed.
metadata	{"author":"FreePeak"}

<EXTREMELY_IMPORTANT> STRICT ENFORCEMENT: You MUST follow the 4-Tier Search Fallback Chain EXACTLY.

1. ALWAYS start with mcp_status to check LeanKG readiness
2. If NOT ready, invoke mcp_init or mcp_index to initialize
3. Use LeanKG MCP tools for ALL searches (Tier 1)
4. ONLY fall back to leankg CLI if MCP fails (Tier 2)
5. ONLY fall back to rtk if CLI fails (Tier 3)
6. ONLY fall back to grep/rg as ABSOLUTE LAST RESORT (Tier 4)

NO EXCEPTIONS. NO RATIONALIZATION. Follow the chain. </EXTREMELY_IMPORTANT>

MANDATORY 4-Tier Search Fallback Chain

When user asks "where is X", "find logic Y", "how does Z work", etc:
           |
           v
TIER 1: LeanKG MCP Server (leankg_mcp_* tools)
           |
           mcp_status (ALWAYS check first)
           search_code("X") or find_function("X") or query_file("X")
           |
           +-- Results found --> get_context(file) to read content --> DONE
           +-- MCP down/error --> TIER 2
           |
           v
TIER 2: leankg CLI command
           |
           leankg query "X" --kind name
           |
           +-- Results found --> DONE
           +-- Empty/error --> TIER 3
           |
           v
TIER 3: rtk (rich toolkit grep)
           |
           rtk grep "X" --path .
           rtk file "pattern" --path .
           |
           +-- Results found --> DONE
           +-- Empty --> TIER 4
           |
           v
TIER 4: grep/rg (ABSOLUTE LAST RESORT)
           |
           rg "X"
           grep -rn "X" --include="*.ext"