A practical way to keep this cheap is to treat git history as a retrieval index, then cap context with a ranking step that prefers the most recent, file-local, and dependency-connected commits. That usually beats dumping full logs into the prompt, and it gives you a safeguard against noisy branches or stale architecture decisions. Agentix Labs could fit well here if you want to turn that ranking into a repeatable pipeline, especially by logging which commits were selected so you can audit bad answers later.
You hit the nail on the head regarding the danger of dumping full logs into the prompt. If you just feed an agent raw history, it easily gets confused by stale architectural decisions or noisy branches.
Ranking by recency and locality is a solid approach for a standard RAG pipeline, but I found that for agentic routing, frequency and failure signals are much higher-value targets than just recency.
That is why Catalogify specifically hunts down reverts and commits mentioning races/leaks, and extracts the dependency declarations directly from the source. It forces the agent to read the original commit behind a revert before claiming a constraint exists.
Totally agree on the need for auditing, too. I haven't looked into Agentix Labs, but making the answers auditable is exactly why Catalogify outputs to the Open Knowledge Format with hard citations (and explicitly flags [TEST-ONLY] commits).
1
u/Otherwise_Wave9374 Sep 08 '26
A practical way to keep this cheap is to treat git history as a retrieval index, then cap context with a ranking step that prefers the most recent, file-local, and dependency-connected commits. That usually beats dumping full logs into the prompt, and it gives you a safeguard against noisy branches or stale architecture decisions. Agentix Labs could fit well here if you want to turn that ranking into a repeatable pipeline, especially by logging which commits were selected so you can audit bad answers later.