I kept finding the same mess in every vibe‑coded repo, so I built a CLI to catch it before I do

Description and use

The rebrief CLI automatically analyzes AI‑generated repositories, detecting stack, commit history, risks, secrets, technical debt, and test coverage, saving two hours of manual effort.

Problem

Freelance developers often inherit projects built with AI tools that contain hidden issues such as hardcoded secrets, unclear stack usage, missing tests, and untracked TODOs, costing about two hours of manual investigation per repo.

Outcome

The CLI automates the initial repo assessment, producing a concise report that replaces two hours of manual investigation.

Workflow

• Run pip install rebrief
• Execute rebrief scan .
• Review the generated REBRIEF.md for stack, history, risk, secrets, debt, TODOs, and test coverage

Evidence

I freelance. Half my work lately is taking over projects built with AI tools like Cursor, Claude, Codex.

Source

Every single time I open one of these repos, the first two hours look the same: scroll through git history, grep for hardcoded API keys, figure out stack, find TODOs, check tests.

Source

rebrief scans a repo and spits out a single REBRIEF.md file with stack detection, filtered git history, a risk map, secrets detection, tech debt and TODO list, test coverage summary.

Source

pip install rebrief rebrief scan .

Source

It also works in a few other modes if that's useful to you: MCP server mode, scan a remote repo by URL, chat mode over the generated report, interactive HTML output, or XML if you need it machine-readable.

Source

It's open source, live on PyPI and GitHub, past v0.3.2. Built it because I needed it myself, not because I had a grand plan. Still rough in places.

Source