Architecture Integrity - across your repos
By: Ran Banker
🧗 The Challenge
- How to unify architecture standards across a large codebase.
- How to uncover legacy code reasoning.
- How to optimize agentic coding assistants to efficiently navigate the codebase.
- How to consistently maintain architecture integrity.
💡 What's cool?
Learn how to handle mulitple repositories, large mono-repos, and extensive codebases with legacy code using a multi-agent solution.
⚠️ Disclaimer & Scope
The aim of this post is to raise awareness of open-source projects and concepts that can be utilized.
Acknowledgment goes to the creators of the solutions listed below. Note that the referenced repositories may change after the time this post was written; please compare with the original sources.
🎯 The Solution
TL;DR
The reposwarm/reposwarm solution enables you to select the repositories you want to scan, builds an index (i.e., a catalog), and then leverages that catalog to orchestrate swarm agents that handle the coding task while adhering to the specifications.
Key Capabilities:
- Build an Architecture Hub Repo: This serves as the central index registry for all the repositories it covers.
- Agents Need Help: Provide a semantic layer (e.g., a repository descriptor) for each repository.
- Consistency: Provide cross-repository steering policies for general concepts, as well as repository-specific policies tailored to unique needs (e.g., coding language nuances).
- Specs Matter: The solution provides version control over the prompts used, allowing for prompt evolution.
- Legacy Archaeology: The solution tracks repository changes based on commit history, helping uncover legacy knowledge regarding software evolution.
- Reduce Token Waste: Prevent repeated rediscovery of repository structures and agent research by generating markdown indexes of project structures.
Architecture
📊 Conclusion & Insights
We no longer need to surrender to the limitations of the past. We can overcome legacy code knowledge gaps, find ways to handle large codebases, and fight to maintain our architecture integrity—in better ways than ever before.
⏭️ Suggested Next Steps
It is worth reading about an additional foundational philosophy, the “LLM Wiki”, which was introduced by Andrej Karpathy and followed by open-source projects like LangChain’s OpenWiki.
🙏 Acknowledgments
- Open Source Solution Repo: reposwarm/reposwarm. Built during Verbit’s hackathon by Moshe, Idan, and Roy. License: Apache License 2.0.
- LLM Wiki by Andrej Karpathy: Gist Link.
- LangChain’s open-source OpenWiki project. License: MIT.
