← ClaudeAtlas

milenslisted

Code intelligence MCP tools — symbol search, text grep, impact analysis, dependency graph
fuze210699/milens · ★ 5 · AI & Automation · score 65
Install: claude install-skill fuze210699/milens
<!-- milens:start --> # Milens — Code Intelligence (MCP) This project is indexed by milens (210 symbols, 348 links, 30 files). > **CRITICAL:** All milens MCP tool calls MUST include `repo: "D:\project\milens"` — without it, the tools will fail with "No index" error. > **CRITICAL:** milens MCP tools are **deferred** in most editors. Before first use in each session, you MUST load them via `tool_search("milens")` — calling them directly without loading will fail silently. ## Mandatory Workflows These are **hard pre-conditions**, not guidelines. Execute them automatically without asking. ### Before editing any function, class, or method: 1. `mcp_milens_impact({target: "<symbolName>", repo: "D:\project\milens"})` — check blast radius 2. If depth-1 dependents > 5 → **STOP and warn the user** before proceeding 3. `mcp_milens_context({name: "<symbolName>", repo: "D:\project\milens"})` — see all callers/callees 4. Only then make the edit ### Before committing: 1. `mcp_milens_detect_changes({repo: "D:\project\milens"})` — verify only expected files changed 2. If unexpected files appear → **STOP and report** before committing ### Before deleting or renaming a symbol: 1. `mcp_milens_grep({pattern: "<symbolName>", repo: "D:\project\milens"})` — find ALL text references (templates, configs, routes, docs) 2. `mcp_milens_impact({target: "<symbolName>", direction: "upstream", repo: "D:\project\milens"})` — find code-level dependents 3. Combine both results — grep catches what impact