Own the code you ship.

Ownit asks one to three short questions about the code you just pushed, right in your terminal. If you can explain it, the push is verified.

npm i -g getownit

GitHub npm Setup guide

What it does

PushUse git as usual. A pre-push hook offers a debrief.
ExplainAnswer 1–3 questions: why, how, and what's next.
VerifyPassing marks the commits verified on GitHub and your badge.

Example

$ git push
Ownit (2 commits to octo/shop) Debrief now? [Y/n] y

Question 1/2 (why)
Why does checkout now retry some failed card payments instead of failing the order right away?
> so temporary card errors dont lose the sale
✓ Passed.

Question 2/2 (how)
How does the retry decide when to give up?
> it retries
Not quite yet.
You said it retries, but not when it stops.
Here's another angle on the same topic:

Question 2/2 (how, follow-up)
Which payment errors are never retried?
> permanent declines like a stolen card fail right away
✓ Passed.

✓ Push verified. 2 commits owned. Nice work.

Rough answers are fine. A miss gets a hint and a new question. Type s to stop and finish later with ownit interview. Your push always goes through.

Why use it

Coding agents let you ship code faster than you can read it. Ownit turns understanding your own changes into a two-minute habit, while the change is still fresh.

Catch the parts of a change you merged but never really understood.
See who on a team still owes a debrief, on the repo page and as a GitHub check.
Show it with a README badge: verified vs. unverified commits.

It is a learning tool. A passed debrief records understanding at the keyboard, not proof of authorship or correctness.

Setup

npm i -g getownit
ownit login       # sign in with GitHub
ownit key set     # Nebius or NVIDIA API key, stays on your machine
cd your-repo
ownit init        # installs the hook, then the GitHub App

Needs Node 20+ and an API key from Nebius Token Factory or NVIDIA. Questions are written and graded by NVIDIA Nemotron.