explaingit

dollspace-gay/vibe-fork

Analysis updated 2026-08-11 · repo last pushed 2026-05-25

11PythonAudience · developerComplexity · 4/5MaintainedSetup · moderate

TLDR

A tool that helps AI rewrite a codebase from one programming language to another while keeping the new version behavior-identical to the original. It runs on top of Claude Code and enforces a strict four-agent loop so translations stay correct, not just plausible.

Mindmap

mindmap
  root((repo))
    What it does
      Translates code between languages
      Enforces correctness via agents
      Blocks writes without source reads
    How it works
      Four-agent loop
      Adversarial critic agent
      Route table maps files
    Use cases
      Port C to Rust
      Port Python to Go
      Translate PyTorch internals
    Audience
      Developers porting codebases
      Correctness-focused projects
      Not for greenfield work
    Notable rules
      No stubs or placeholders allowed
      Verification by failing tests
      Language-agnostic harness

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Port a C program to Rust while verifying edge-case behavior matches the original.

USE CASE 2

Translate a Python library to Go with an adversarial agent catching subtle differences.

USE CASE 3

Rewrite PyTorch C++ internals into a Rust ML framework using the four-agent loop.

USE CASE 4

Translate Linux kernel C code into Rust with failing tests pinning every divergence.

What is it built with?

PythonClaude Code

How does it compare?

dollspace-gay/vibe-fork2arons/llm-cliabe238/claude-video-plus
Stars111111
LanguagePythonPythonPython
Last pushed2026-05-25
MaintenanceMaintained
Setup difficultymoderateeasyeasy
Complexity4/52/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires Claude Code as the underlying AI coding tool and an existing codebase to port from, it does not work for greenfield projects.

No license information is provided in the explanation, so usage terms are unknown.

In plain English

vibe-fork is a tool for AI-assisted code translation. When you want to rewrite a working codebase from one programming language to another, like porting a C program to Rust, or a Python library to Go, this tool sits on top of Claude Code and enforces enough discipline that the translated version actually behaves the same as the original, not just looks similar. The core problem it solves is "vibe translation": an AI reads the source once, writes target code that compiles, but silently mishandles edge cases like how numbers overflow or how errors propagate. The tool fixes this with a strict four-agent loop. One agent writes the code, a second agent acts as an adversarial critic hunting for subtle differences from the original, a third applies minimal fixes, and a fourth manages design docs. Before any code is written, background hooks check that the AI has actually read the source file and the design plan. If it hasn't, the write is blocked. You'd use this if you're porting something substantial where correctness matters. The README cites two real projects built with it: translating PyTorch's C++ internals into a Rust ML framework, and translating Linux kernel C code into Rust. If you're starting something new with no existing code to port from, this tool explicitly isn't for you. What's notable is the mechanical rigor. There are no stubs allowed, no todo() markers or placeholder functions that compile but do nothing. The route table maps every target file back to its upstream source, so nothing gets written in a vacuum. Verification is always a failing test that pins a specific divergence, not a paragraph of prose claiming things match. The whole setup is language-agnostic, so the same harness works regardless of what you're translating from or to.

Copy-paste prompts

Prompt 1
I want to port my C project to Rust using vibe-fork. Walk me through how to set up the four-agent loop and route table so every Rust file maps back to its C source.
Prompt 2
Set up vibe-fork to translate my Python library into Go. Show me how to configure the design-doc agent and the adversarial critic so edge cases like integer overflow are caught.
Prompt 3
Help me use vibe-fork to port a Linux kernel module from C to Rust. Explain how the pre-write hooks enforce that Claude Code has actually read each source file before generating code.
Prompt 4
I have a working C++ codebase I want to translate to Rust with vibe-fork. Generate the verification test plan so each test is a failing test that pins a specific behavioral divergence from the original.

Frequently asked questions

What is vibe-fork?

A tool that helps AI rewrite a codebase from one programming language to another while keeping the new version behavior-identical to the original. It runs on top of Claude Code and enforces a strict four-agent loop so translations stay correct, not just plausible.

What language is vibe-fork written in?

Mainly Python. The stack also includes Python, Claude Code.

Is vibe-fork actively maintained?

Maintained — commit in last 6 months (last push 2026-05-25).

What license does vibe-fork use?

No license information is provided in the explanation, so usage terms are unknown.

How hard is vibe-fork to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is vibe-fork for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.