Hokmah Code Impact
What it does
Before you change code, Hokmah tells you what else is likely to move. It builds a graph of a repository from its file tree and its recent commit history — which files and modules have historically changed together — and, given a plain-language description of a change, returns a risk assessment, the files, symbols and modules likely to be affected, and the related commits. The analysis is a graph computation: no language model is called, and nothing is sent to an AI provider.
Connect
In Claude: Settings → Connectors → Add custom connector, URL:
https://mcp.hokmah.dev/mcp
No sign-in is needed. Only public GitHub repositories are supported.
Tools
| Tool | What it does |
|---|---|
hokmah_connect_project | Imports a public repository: indexes its source files and its latest commits (up to 500) from the default branch. Done once per repository; later calls report it as already imported. |
hokmah_analyze | Estimates the impact of a described change on an imported repository: risk, affected files, symbols, modules and related commits. Read-only. |
Typical use
- Before a refactor: “rename the session middleware” → which files and tests are historically coupled to it.
- Reviewing a pull request: describe the change and compare the predicted blast radius with what the PR actually touches.
- Finding where a bug hides: describe the symptom's area and get the modules that change with it.
Limits
- Public GitHub repositories only. Visibility is checked with GitHub at import and at every analysis; a repository that becomes private stops being served.
- Indexed source types: .py .js .ts .jsx .tsx .rs .go .java. History: the latest 500 commits of the default branch.
- Rate limits per client address: 60 analyses and 5 imports per hour (plus a server-wide import cap).
- Imported repository graphs are shared: once a public repository is imported, any user can analyze it.
Privacy & support
Privacy policy · Support: freddavidblum@catalystais.com