Back
Advanced // Repository Intelligence
Repository Intelligence
Docs › Advanced › Repository Intelligence
Repository Intelligence
NOVA builds a private map of how your project connects: what depends on what, what calls what, and what a change could affect. It uses the map automatically, so answers hold for the whole codebase.
It works automatically
You don't have to do anything. In existing projects, NOVA uses the map for architecture, impact and cross-file questions.
Ask the map yourself
nova
\map # the project's structure
\trace calculateTotal # where it's defined, called and used
\impact src/billing/invoice.py # what a change could affect
\trace calculateTotal # where it's defined, called and used
\impact src/billing/invoice.py # what a change could affect
Private and local
- The map is built and kept on your computer.
- Your code is read, never run, to build it.
- If the map isn't available, NOVA falls back to ordinary search and keeps working.
Manage it
bash
nova intelligence status # is it ready and up to date?
nova intelligence refresh # update it
nova intelligence rebuild # rebuild it from scratch
nova intelligence off # use ordinary search only
nova intelligence on # always use it when relevant
nova intelligence clear --yes
nova intelligence refresh # update it
nova intelligence rebuild # rebuild it from scratch
nova intelligence off # use ordinary search only
nova intelligence on # always use it when relevant
nova intelligence clear --yes
Inside NOVA, use \intelligence status and the same words.
If nova doctor reports a problem with it:
bash
nova doctor --repair-intelligence
Join our Discord
Chat with our engineers and become part of the active NOVA developer community.
Need help?
Open an issue on GitHub or email support@bridgeye.com.