> For the complete documentation index, see [llms.txt](https://docs.visdom.virtuslab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.visdom.virtuslab.com/visdom-context-fabric/user-guide/repo-insights-module.md).

# Repo insights module

This module is enabled per repository. Its goal is to extract non-obvious, non-standard information from a codebase. Each analyzer contributes a section to the data returned by the `repo_insights` MCP tool for that repository. The information is refreshed daily and incrementally.

Four analyzers can be enabled:

* `git`: identifies files that often change together, and hotspots, the files changed most often. A hint to the agent about which files probably need editing together.
* `vocabulary`: an ubiquitous-language-inspired list of the top 20 non-trivial terms used in the repository, with their definitions.
* `scg`: Java only. The top five in-degree classes, the most referenced ones, and cross-package divergence.
* `comments`: tribal knowledge mined from the repository's comments: work-arounds, warnings and invariants that keep being repeated.

![Repo insights for a repository: files that change together, and tribal knowledge mined from its comments](https://1398155133-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FED9nLcXxDQR0x7nt8zMS%2Fuploads%2FnjuLyISqK0n1iMKs8ARV%2Frepo-insights.png?alt=media)

{% hint style="warning" %}
Except for `git`, the analyzers lean heavily on LLM judgment, so a large repository can cost real money on the first run. Later runs are incremental.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.visdom.virtuslab.com/visdom-context-fabric/user-guide/repo-insights-module.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.