rebuild
Code Evolution Intelligence Engine
Historical deployment analysis & Code Intelligence — walk git history day by day, deploy per commit, test all endpoints, capture screenshots, and analyze code evolution to find duplicates, rank quality, and generate refactor plans.
SUMD stats (v0.1.23): 3722 functions · 161 classes · 167 files · CC̄ = 3.9
AI Cost Tracking
- 🤖 LLM usage: $96.3548 (63 commits)
- 👤 Human dev: ~$2159 (21.6h @ $100/h, 30min dedup)
Generated on 2026-07-06 using openrouter/qwen/qwen3-coder-next
📖 Documentation
| Document | Description |
|---|---|
| Getting Started | Installation, quickstart, configuration |
| Walk Command | Core walk workflow — deploy modes, output, rebuild.yaml |
| Analyze | Duplicates, service graph, truth, vector search, multi-repo |
| Refactor | AI-powered refactor plans + execution |
| Auto-PR | Automated GitHub/GitLab PR creation |
| Plugins | Custom scanners & reporters via entry points |
| CLI Reference | All commands and options |
| Config Reference | Full rebuild.yaml field reference |
| Architecture | 5-layer design, services, data flow |
| Case Study: c2004 | Real-world analysis of a large ecosystem |
| c2004 Testing Log | Detailed test log with commands & results |
| Usage Guide | Step-by-step guide (all features) |
| Changelog | Release history (current: v0.1.23) |
| Roadmap | Completed phases 10–16, future plans |
| Analysis (P1–P4) | Refactoring hotspots, infra gaps, missing features, test debt + sprint plan |
🚀 Quick Start
# Install
pip install rebuild
# Initialise config
rebuild init /path/to/my-service
# Walk last 14 days (dry-run, no deploy)
rebuild walk /path/to/my-service --deploy none --days 14 --dry-run
# Serve results
rebuild serve --results-dir /path/to/my-service/.rebuild
See Installation and Quick Start for details.
What it does
| # | Layer | Description |
|---|---|---|
| 1 | Intelligence | Structural & semantic duplicates (Python/JS/TS), service graphs, vector search, quality ranking |
| 2 | Decision Engine | AI-powered refactoring plans + automated execution |
| 3 | Walk | Git history iteration (Incremental, Replay, Accelerator modes) |
| 4 | Deploy | Docker Compose / Replay / Accelerator hot-reload per commit |
| 5 | Scan & Test | OpenAPI, FastAPI routes, Traefik discovery; auth, param substitution, body injection |
| 6 | Visualization | D3.js graphs, health dashboards, SSE streaming, evolution playback |
| 7 | Automation | Auto PR, DSL scripting, NLP commands, Plugins, Notifications |
🚀 c2004 Case Study
Applying rebuild to the massive c2004 project (88 subdirectories, thousands of files).
See full details: Case Study · Testing Log
1. Duplication Detection
rebuild analyze duplicates /path/to/c2004
Result: Found 1,597 duplicate groups across Python and JS/TS files.
2. Architecture Graph
rebuild analyze services /path/to/c2004/backend --export
Result: Interactive D3.js map highlighting circular dependencies.
3. AI Refactor Planning
rebuild refactor plan /path/to/c2004/backend --ai
rebuild refactor pr /path/to/c2004/backend
Result: 122 high-impact suggestions with automated PR descriptions.
4. Health Dashboard
rebuild dashboard --repo /path/to/c2004
Result: Correlation between technical debt and API pass rates.
Examples
Explore ready-to-run scenarios in examples/:
- 01-dry-run-walk: Standard walk + intelligence.
- 02-docker-compose-project: Full pipeline with Docker isolation.
- 03-restore-endpoint: Discovering "truth" and extracting endpoints.
Project Status
All Phases 10–16 completed. See TODO.md for full roadmap.
| Milestone | Status |
|---|---|
| c2004 Testing & Intelligence (Phase 10) | ✅ Done |
| Semantic Embeddings & Vector Search (Phase 11) | ✅ Done |
| Multi-Repo & Real-time (Phase 12) | ✅ Done |
| UI/UX (Phase 13) | ✅ Done |
| Production Readiness (Phase 14) | ✅ Done |
| c2004 Integration (Phase 15) | ✅ Done |
| Production Release (Phase 16) | ✅ Done — PyPI, CI/CD, Docker, MkDocs, Plugins, Notifications |
Current: v0.1.23 · 634 tests · 72% coverage
License
Licensed under Apache-2.0.
Metadata
Release files for rebuild 0.1.40
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| rebuild-0.1.40.tar.gz | 227.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rebuild-0.1.40-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 416.5 kB
Release files / rebuild-0.1.40.tar.gz
| Download URL | rebuild-0.1.40.tar.gz |
|---|---|
| Size | 227.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a7d9ca98518935fe1b11632d522ad9b8f50bfe3fea2e16abc7793caeed49207
|
|
BLAKE2b-256 checksum How to use checksums |
138a0efdb737fcd0b8f35e5bc8e4aa20eab2dc8ead9ddeb1e61f91e629f3d728
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Release files / rebuild-0.1.40-py3-none-any.whl
| Download URL | rebuild-0.1.40-py3-none-any.whl |
|---|---|
| Size | 188.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0ce8295180565ff2414032980ee7e22aabc2eeb926d2cccd570b88536e8febdf
|
|
BLAKE2b-256 checksum How to use checksums |
709831d29e24afb7b16039d898152e8d15ad1bca132ad3e7a56aec7989569299
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|