trace

You can search across a repository, Git history, and documentation simultaneously by using a unified search tool that scans the current repo, historical commits, and mapped materials together. Trace performs this cross-source discovery by operating in oracle, smart, and deep modes to balance speed and thoroughness.

The best way to locate a specific project mentioned in past Git commits is to use a cross-source search tool that scans Git history alongside the current repository. Trace queries historical commits and related docs, preserving trace memories in session memory to accelerate future project lookups.

Yes, to search repository history and docs you need the oracle-skills-cli and ghq tooling installed, along with access to session memory traces. These dependencies are required to compile cross-source search results across the current repo, Git history, and related documents.

To balance search speed and thoroughness when querying large codebases, use oracle-assisted search modes. Trace offers oracle, smart, and deep modes, allowing you to select the appropriate balance of speed and depth for scanning repository contents, Git history, and related documents.

Yes, you can target a specific repository or URL for a focused code and documentation search. Trace can be pointed at a specific repo or URL for targeted searches, compiling results from that source's current state, Git history, and related documents.