Skip to content

Vibe2Vibe

The vibe2vibe evaluates the total code complexity of a given source code repository on several measures (cyclomatic complexity etc.), then uses this to split the resulting application into smaller microservices.

Code Video Cerebral Valley

Core trick

Computes cyclomatic complexity per module, then assigns each proposed microservice its own guardian agent with bounded context.

Tags

dev toolsagents

Description

The vibe2vibe evaluates the total code complexity of a given source code repository on several measures (cyclomatic complexity etc.), then uses this to split the resulting application into smaller microservices. To showcase this for a real applicatoin, we created the Banana Scanner (an LLM Brand Presence Test application we created) as an example target.
kirilligum/vibe2vibe-hackathon-251206★ 00 forksTypeScriptMITCreated Dec 6, 2025 · last push Dec 7, 2025

README excerpt

# Vibe2Vibe 🌊✨

**Automated Monorepo Refactoring & Complexity Analysis System**

**Architecture Specification | Version 1.0**

Welcome to the **Vibe2Vibe** project repository, created for the Hackathon (December 2025). This project aims to revolutionize how legacy codebases are analyzed and refactored by combining advanced cyclometric analysis with autonomous AI agents.

## 👥 Team
- **Ari**
- **Kirill**
- **Ted**

---

## 1. Executive Summary

Vibe2Vibe is an agentic web application designed to scalably refactor large codebases into decoupled microservices. It overcomes the "God Agent" hallucination problem and context window limits (100k tokens) by employing a **Multi-Agent System (MAS)** where specific agents act as "Guardians" of individual microservices.

The system relies on a hybrid protocol architecture:
*   **A2A (Agent-to-Agent):** For horizontal coordination, task delegation, and negotiation between agents (e.g., Architect Agent $\leftrightarrow$ Service Agent).
*   **MCP (Model Context Protocol):** For vertical execution, allowing agents to use tools like file system access and metric calculators (Grazer).

---

## 2. System Components

### A. The Agents (The "Guardians")
Every microservice (or repo folder) is assigned a dedicated **Service Agent**.
*   **Role:** Acts as the "Lead Developer" for that specific service.
*   **Context:** Only loads the code relevant to its service (< 100k tokens).
*   **Constraint:** Cannot edit files outside its folder. Must send **A

Team