Skip to main content
You’ve been shipping code for weeks (months? years?), but when someone asks “what have you been working on lately?”—you draw a blank. You know you built something important, but the details are fuzzy. That’s where repr comes in. It reads your git history and turns your commits into professional narratives. Here’s how to get your first stories generated in about 5 minutes.

​
What You’ll Need

  • The repr CLI installed (see Installation if you haven’t yet)
  • A folder with some git repositories (like ~/code or ~/projects)
  • (Optional) Ollama running locally if you want 100% offline generation
Let’s go.
1

Scan your repos

Point repr at your code directory and let it discover what you’ve been working on.
Repr will scan for git repositories and show you what it found:
Hit enter to confirm. Your repos are now tracked, but nothing has left your machine yet—this is all local.
2

Take a quick look around

Before generating anything, let’s see what you’ve been up to this week.
You’ll get a quick summary like:
This is just a preview—nothing saved yet. But it gives you a sense of what repr will work with.
3

Generate your first stories

Now for the magic. Let’s turn those commits into professional narratives.
If you don’t have a local LLM installed, repr will guide you through setting up Ollama or adding an API key (OpenAI, Anthropic, etc). Your choice.
You’ll see repr processing your work:
That’s it. You’ve got professional summaries of your work, stored locally as JSON files.
4

Check out your stories

See what got generated.
You’ll get a list with IDs, dates, and titles:
Want to see the full story? Pick an ID and view it:
You’ll see a markdown-formatted story with context, technologies used, and impact.

​
What Just Happened?

You just turned your messy git history into clean, professional narratives. Here’s what repr did:
  1. Scanned your commits - Read commit messages, diffs, and file changes
  2. Grouped related work - Identified logical units (features, fixes, refactors)
  3. Generated context - Used an LLM to write professional summaries
  4. Saved locally - Everything lives in ~/.repr/stories on your machine
Nothing was uploaded anywhere. Your code stays on your machine. The only network call was to your local LLM (if you used --local) or to your API provider (if you used your own key).

​
What’s Next?

Now that you’ve got stories, here’s what you can do: The power move? Set up git hooks and let repr track everything automatically. Then, once a week, review and publish your best work. Five minutes a week to maintain a living portfolio of what you’ve actually built.