Inspiration
GitHub is filled with promising repos that stall before reaching production quality. We wanted to eliminate the gap between idea and operational software by creating an AI engineering team that finishes what developers start. RepoMan is inspired by the belief that software delivery should be continuous, autonomous, and self-improving — not dependent on sustained human momentum.
What it does
RepoMan ingests any repository and transforms it into an enterprise-grade project. A multi-model agent council audits the codebase, debates architecture decisions, reaches consensus, then implements fixes, tests, documentation, CI/CD, and optimization. Elasticsearch provides deep repo indexing, semantic search, analytics, and visibility into repo health and transformation progress.
How we built it
We built RepoMan as an agentic orchestration system in Python using a council architecture (Architect, Auditor, Builder, Orchestrator). Elasticsearch powers repository ingestion, code indexing, semantic retrieval, and analytics dashboards. The system clones repos, parses structure, generates audit reports, runs a consensus loop, executes improvements in a sandbox, validates builds, and logs outcomes into a learning memory layer for future runs.
Challenges we ran into
Designing a reliable consensus loop between multiple models was complex — preventing infinite debate while preserving critique quality required structured scoring and arbitration rules. Executing code safely demanded sandboxing and reproducible environments. Another challenge was mapping heterogeneous repos into a unified analysis pipeline and building Elasticsearch schemas flexible enough to support multiple languages and signals.
Accomplishments that we're proud of
We built a working end-to-end pipeline that can ingest repos, index them in Elasticsearch, generate structured audits, and demonstrate the consensus-driven improvement workflow. RepoMan makes the reasoning process visible — showing agent debate, decisions, and measurable quality improvements. We created a foundation for autonomous software delivery rather than one-shot code generation.
What we learned
Autonomous engineering is less about generation and more about evaluation loops. Multi-model critique dramatically improves output reliability. Search infrastructure (Elasticsearch) is critical for agent memory, traceability, and system observability. Clear execution boundaries and validation layers are essential for trust in AI-driven code changes.
What's next for RepoMan
Next we are expanding RepoMan into a continuous repo maintenance platform that runs as a background agent on GitHub projects. Planned work includes deeper CI/CD automation, security remediation, pull-request generation, longitudinal repo health scoring, and self-learning improvement patterns across thousands of repositories — moving toward fully autonomous software lifecycle management.
Built With
- anthropic
- astparsing
- chromadb
- crewai
- docker
- elasticsearch
- fastapi
- gemini
- githubactions
- langgraph
- ollama
- openai
- python
- react
- semgrep
- tree-sitter
- vectorsearch
Log in or sign up for Devpost to join the conversation.