neracu/rebrief
Local CLI that scans a codebase and writes a structured markdown handoff report.
Tested on Linux
Use it
Linux x86_64
install rebrief via uv tool install
uv tool install rebrief
Check that it works
rebrief --version 2>&1; rebrief --help 2>&1The output should contain “rebrief, version 0.3.2”.
First thing to try
mkdir -p /tmp/testrepo && cd /tmp/testrepo && git init -q && git config user.email "test@example.com" && git config user.name "Tester"
cat > package.json <<'EOF'
{"name":"testapp","version":"1.0.0","dependencies":{"react":"18.0.0","express":"4.18.0"}}
EOF
cat > requirements.txt <<'EOF'
flask==3.0.0
fastapi==0.110.0
EOF
cat > go.mod <<'EOF'
module example.com/app
go 1.21
require github.com/gin-gonic/gin v1.9.1
EOF
mkdir -p src
cat > src/app.py <<'EOF'
# TODO: refactor this module
API_KEY = "sk_test_1234567890abcdef1234567890abcdef"
def hello():
# FIXME: handle errors
pass
EOF
echo "# Test Repo" > README.md
git add . && git commit -qm "Initial commit: add stack manifests"
echo "minor change" >> README.md && git commit -am "fix typo" -q
echo "feature code" > src/feature.py && git add . && git commit -qm "feat: add feature module with important logic"
echo "done" && ls -R /tmp/testrepo
rebrief badge /tmp/testrepo 2>&1Run rebrief scan <repo> -o <file> to scan a repository and write a Markdown report.
What it does
- Scan a codebase and write a Markdown reportTested
How to use it
- Run
rebrief scan <repo> -o <file> --no-blame --skip-vulnerability-checkto scan the repository and save the report. - Open the report file. It starts with a "REBRIEF REPORT" heading for your repository.
- Run
- Detect the tech stack from manifest filesTested
How to use it
- Run
rebrief scan <repo> -f json -o <file> --no-blame --skip-vulnerability-checkto get a JSON report. - Look at the
tech_stacksection for languages, frameworks, manifests and dependencies.
- Run
- Show the Git history timeline and hotspotsTested
How to use it
- Run
rebrief scan <repo> -f json -o <file> --no-blame --skip-vulnerability-checkto get a JSON report. - Look at the
timelinesection for the commit history.
- Run
- Find hardcoded secrets and technical debtTested
How to use it
- Run
rebrief scan <repo> -f json -o <file> --no-blame --skip-vulnerability-checkto get a JSON report. - Look at the
risk_mapsection for secrets and technical debt findings.
- Run
How far pickfit got
Linux x86_64
- Installs
- Starts
- 4 of 4 features work
- Works offline
Good for
- scan a local repo or remote Git URL
- detect tech stack and dependencies across ecosystems
- map secrets, technical debt and missing tests
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
Its main function works
- Replayed from scratch
- Works offline
- Checked on 1 Nov 2026
- Version 0.3.2