pickfit

BrowseDeveloper CLIs

NPIAC

Turns a local repo into a compact deterministic CONTEXT.md briefing for coding agents.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Python>=3.11
  1. Clone NPIAC source for pip install

    git clone https://github.com/dRafaleD/NPIAC.git /tmp/NPIAC
  2. Install NPIAC with pip from source

    cd /tmp/NPIAC && python3 -m pip install .

Check that it works

npiac --help

The output should contain “usage: npiac”.

First thing to try

mkdir -p /tmp/sample-api/src/sample && cat > /tmp/sample-api/pyproject.toml <<'EOF'
[project]
name = "sample-api"
version = "0.1.0"
dependencies = ["fastapi", "uvicorn"]

[project.scripts]
sample-api = "sample.main:main"
EOF
cat > /tmp/sample-api/src/sample/main.py <<'EOF'
from fastapi import FastAPI
app = FastAPI()

@app.get("/")
def read_root():
    return {"hello": "world"}

def main():
    import uvicorn
    uvicorn.run(app)
EOF
cat > /tmp/sample-api/requirements.txt <<'EOF'
fastapi
uvicorn
EOF
ls -R /tmp/sample-api
npiac /tmp/sample-api --stdout

Run npiac <repo-path> --stdout to print a context briefing for a repository.

What it does

  • Generate a context briefing for a repository
    How to use it
    1. Run npiac <repo-path> --stdout to print the Markdown briefing.
    2. Read the output, which starts with "# Repository Context".
    Tested
  • Detect languages, frameworks, and entry points
    Not shown working
  • Add architecture notes using local Ollama
    Not tested
  • Limit context size with a budget
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 1 of 4 features work
  4. Works offline

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • Generate deterministic context in the current repository
  • Print repository context Markdown without writing a file
  • Limit final context size with a character budget

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 30 Oct 2026
  • Version 0.6.0

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.