PIP: the performance review where the AI reviews you
Every AI tool reviews your code. PIP reviews the programmer.
Every developer keeps a work diary without knowing it: their git history. Every change is in there, with a timestamp and a little note that was supposed to explain it. PIP reads that record, locally, on your own machine, and issues a formal manager-style performance review. With evidence.
pip install on-a-pip
Then, inside any git repository:
on-a-pip
PERFORMANCE IMPROVEMENT PLAN - Dev Example
pip-sample | 8 commits reviewed | 2025-10-14 to 2026-11-08
--------------------------------------------------------------
Communication F 32.5 ######
Reliability C 64.4 ############
Follow-through B 84.3 ################
Judgment B 83.8 #################
Consistency D 43.0 ########
--------------------------------------------------------------
OVERALL C 61.6
Meets some expectations. There is a conversation to be had.
(That is a real review of a deliberately terrible sample history. Yours will be different. Possibly worse.)
What it grades
- Communication. How many of your commit messages actually say anything. "stuff", "wip" and "asdf" are entered into the record, quoted back at you.
- Reliability. Commits between 10pm and 5am. Commits shipped Friday after 4pm. Reverts. Chains of commits that start with "fix".
- Follow-through. The TODOs still sitting in your code, and how old the oldest one is. A TODO that has been waiting 400 days has seniority.
- Judgment. The spots labelled "temporary", "hack" or "workaround", and how long the oldest one has been load-bearing.
- Consistency. Active days versus silent stretches, longest streak, longest disappearance.
Then it does what any good PIP does: it writes you a 30-day improvement plan, generated from your three weakest categories, and signs off with the only appeal process that has ever worked: improve the record.
Outputs
on-a-pip ~/some/repo --md review.md --html card.html
on-a-pip --author "your name" # review one author (default: the most prolific)
on-a-pip --json # machine-readable review
- The terminal summary above.
- A full formal review in Markdown: per-category evidence, management notes, the plan, the sign-off.
- A shareable report card in HTML (see
examples/), made for posting. Every card is different, because every history is different.
Sample outputs live in examples/: a full sample review, a sample report card, and a real report card generated from the Decksmith repository.
Private by construction
PIP runs git log, git grep and git blame on your machine and nothing else. No network, no account, no API key, no telemetry, pure Python standard library. Your history is embarrassing enough without uploading it somewhere.
Requirements
- Python 3.9+
- git, on your PATH
Honest notes
- The package is called
on-a-pipbecause PyPI rejectedpip-pipas too similar topipitself, which is fair: you do not get to out-pip pip. The tool was going to bepip install pip-pip. Now you install the news that you are on one. - Grades are deterministic: same history, same review. The formulas are plain arithmetic in one file,
pip_pip.py, if you want to argue with them. - PIP reviews the most prolific author in the repo by default. Use
--authorin shared repos.
License
MIT. Built by Ghost Developer Studio.
Metadata
Release files for on-a-pip 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| on_a_pip-0.1.0.tar.gz | 15.1 kB | With provenance | Details for on_a_pip-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| on_a_pip-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for on_a_pip-0.1.0-py3-none-any.whl |
Total release size: 28.6 kB
Release files / on_a_pip-0.1.0.tar.gz
| Download URL | on_a_pip-0.1.0.tar.gz |
|---|---|
| Size | 15.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d5f099d781d706669be8a1176410205f21380ab6dd522e1bada90ec60bc126ef
|
|
BLAKE2b-256 checksum How to use checksums |
a96e66c03da6f57fe2587ebeee50a8902ce479f648ad6b432526f6eb042d91ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.
Transparency logRelease files / on_a_pip-0.1.0-py3-none-any.whl
| Download URL | on_a_pip-0.1.0-py3-none-any.whl |
|---|---|
| Size | 13.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a335de77d1a028f8a2cbcf3a4d62d5de296300ec4a25bebfaf27962301b06936
|
|
BLAKE2b-256 checksum How to use checksums |
3e42ab004ef637d5962db1b3d5f2ae7704841afa0f65c96b982fa6dff409a760
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.
Transparency logSecurity for on-a-pip 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for on_a_pip-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.