Skip to main content
Here’s the thing about tracking your work: if it takes more than 5 seconds, you won’t do it. You’re busy shipping code, not maintaining a work journal. Repr solves this by making tracking invisible. Once you set it up, it just works in the background. Here are three ways to fit repr into your daily flow, from fully automatic to totally manual. Install git hooks once. From then on, every commit you make gets silently queued for story generation—no interruptions, no network calls, just quiet tracking.
1

Install hooks everywhere

One command to install hooks in all your tracked repos:
That’s it. Now when you run git commit, repr adds that commit to a local queue in the background. You won’t even notice it happening.What gets sent where? Nothing. The hook just writes to ~/.repr/queue on your machine. No network activity.
2

Generate stories when you're ready

At the end of your day (or week, or whenever), turn the queue into stories:
Repr reads the queued commits, groups related work, and generates professional summaries using your local LLM.
3

Review and approve

New stories are marked as “needs review” by default. Check them out:
Or use the interactive review flow:
You’ll be walked through each story with options:
Press a to approve, e to edit in your $EDITOR, or r to regenerate with different context.
Pro tip: Run repr generate on Friday afternoons. Review your week’s work in 2 minutes, then export it as your weekly update for your manager or team.

​
Option 2: Quick Morning Standup

Don’t want hooks? No problem. Use repr as your standup prep tool.
This gives you a quick summary of the last 3 days—perfect for answering “what did you work on yesterday?”
Want to generate stories from these commits?
Now they’re permanent stories in your ~/.repr/stories folder.

​
Option 3: End-of-Day Capture

Maybe you don’t want automatic hooks, but you do want to capture your work at the end of each day. That’s the sweet spot for a lot of people.
Output:
Like what you see? Generate stories from them:
Or get even more specific:

​
Which Workflow Should You Use?

Here’s how to think about it:
WorkflowBest ForTime Investment
Hooks (automatic)People who want zero friction1 min setup, then nothing
Morning reviewPeople who like morning rituals30 seconds daily
End-of-dayPeople who batch work at day’s end2 minutes daily
The honest truth? Most people start with repr commits --days 3, realize they want it automated, and switch to hooks. But all three work great—pick what fits your style.

​
What Happens Next?

Once you’ve got stories being generated regularly, you can: The key is: start capturing now. Future you will thank present you when it’s time to update your resume, prep for a review, or answer “what have you been working on?”