For people who write software
Your CV, from the work you actually shipped.
Your own coding agent reads your git history and coding-agent sessions on your machine and writes one file. cv0 turns it into records you check, then builds a CV for each job from them.
{
"source": "git",
"ref": "[employer]/payments#412",
"project": "payments",
"date": "2025-03-18",
"said_by": "user",
"text": "Merged: move order events from the monolith to a Kafka consumer, with replay for failed messages"
}read by cv0
How it works
Four steps, and your agent does the reading.
- 01
Get the prompt.
On My experience, under Evidence sources, copy a two-line prompt into your coding agent.
- 02
Your agent collects.
It reads git in your repositories, by your git name and emails. If gh is already signed in, merged pull requests replace the commits they cover. For sessions it runs omnirecall, which reads Pi, Claude Code, Codex and OpenCode sessions. It writes cv0-evidence.json.
- 03
You hand it over.
Drop the file on My experience, or send it with a one-time line that works once, within 24 hours.
- 04
cv0 sorts it.
Each finding is checked: is it your work, and which job does it belong to? Work lands under that job, or as a project of your own. You review every record on My experience.
What counts as what
Shipped is not the same as written.
Git shows what changed. Sessions show what you decided, what you ruled out and what you fixed, in your own words. Both are optional; git alone is enough.
- Merged pull request or default-branch work
- You built it.
- Release or tag
- It shipped, on that date.
- A commit on its own
- You wrote it.
- Commit and line counts
- Context only, never a line on your CV.
Privacy
What leaves your machine.
- Your agent does the reading. cv0 never signs in to GitHub or connects to your repositories, and the agent is told never to sign in to anything.
- cv0 receives the findings file: commit messages, pull request descriptions and session messages, each with its date and reference. Not your code.
- Before saving, the agent replaces client, employer and internal product names, people and confidential figures with placeholders, and drops secrets and private URLs. Your own open-source projects stay as they are.
- Nothing is sent until you drop the file or run the send line.
Then, the same as everyone
Paste a job. See where you fit.
Each requirement is marked strong, weak or missing, and you get a CV and cover letter built from your records. Your merged work sits beside your CV, so a requirement your CV never mentioned can still be met.
Questions
No. Git alone works. Sessions add the why behind the work.
One that can run shell commands on your machine, such as Claude Code.
Only yours, by your git name and emails. Other people’s work is context, not your record.
A 4,076-commit import took about nine minutes. Reading findings uses the AI allowance.
It helps. Your CV gives the roles and dates; git and sessions add what you shipped in them.