LunaForge

Documentation

Install the local preview, ask the first impact question, and understand the current limitations.

Start with one safe-change question

After installation, fully quit and reopen Cursor. Open an existing repository and ask:

Use LunaForge to tell me what could break if I change src/path/to/file.ts. Do not edit yet.

MCP tools

  • lunaforge_index_repository — build the local import graph.
  • lunaforge_analyze_change_impact — list direct and transitive dependents.
  • lunaforge_trace_dependency_path — explain how two files are connected.
  • lunaforge_explain_architecture — summarize modules, cycles, and hotspots.
  • lunaforge_time_travel — inspect relevant Git history.
  • lunaforge_autopsy — correlate an error with files and recent changes.
  • lunaforge_guardian_check — evaluate explicit architecture deny rules.
  • lunaforge_create_change_receipt — export evidence for review.

Supported source

The preview resolves common local imports for TypeScript, JavaScript, and Python. Dynamic loading, reflection, runtime-only relationships, generated code, aliases, and framework magic may require explicit configuration or remain unresolved.

Guardian policy

{ "rules": [{ "id": "domain-no-ui", "fromPattern": "src/domain/**", "toPattern": "src/ui/**", "effect": "deny" }] }

Downloads