pickfit

BrowseDeveloper CLIs

neracu/rebrief

Local CLI that scans a codebase and writes a structured markdown handoff report.

Tested on Linux

Use it

Linux x86_64

  1. install rebrief via uv tool install

    uv tool install rebrief

Check that it works

rebrief --version 2>&1; rebrief --help 2>&1

The 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>&1

Run rebrief scan <repo> -o <file> to scan a repository and write a Markdown report.

What it does

  • Scan a codebase and write a Markdown report
    How to use it
    1. Run rebrief scan <repo> -o <file> --no-blame --skip-vulnerability-check to scan the repository and save the report.
    2. Open the report file. It starts with a "REBRIEF REPORT" heading for your repository.
    Tested
  • Detect the tech stack from manifest files
    How to use it
    1. Run rebrief scan <repo> -f json -o <file> --no-blame --skip-vulnerability-check to get a JSON report.
    2. Look at the tech_stack section for languages, frameworks, manifests and dependencies.
    Tested
  • Show the Git history timeline and hotspots
    How to use it
    1. Run rebrief scan <repo> -f json -o <file> --no-blame --skip-vulnerability-check to get a JSON report.
    2. Look at the timeline section for the commit history.
    Tested
  • Find hardcoded secrets and technical debt
    How to use it
    1. Run rebrief scan <repo> -f json -o <file> --no-blame --skip-vulnerability-check to get a JSON report.
    2. Look at the risk_map section for secrets and technical debt findings.
    Tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 4 of 4 features work
  4. 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

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.