Summarise Your Git Log for a Daily Standup
Staring at a dense git log five minutes before standup isn't the best way to remember what you did yesterday. Let Claude summarise it for you.
git log --since="yesterday" --oneline --author="$(git config user.email)" | \
claude -p "Summarise these commits into 2-3 bullet points suitable for a standup update. Be concise and focus on what was accomplished, not the implementation details."
The output will be something your team actually wants to hear — grouped by theme, written in plain English, free of commit message noise like "wip", "fix typo", and "more changes".
You can extend the window for a weekly summary:
git log --since="1 week ago" --oneline | \
claude -p "Give me a brief weekly summary of this work, suitable for a Friday progress update."
Or pull from multiple repos if your work spans them:
(cd ~/projects/api && git log --since="yesterday" --oneline; \
cd ~/projects/frontend && git log --since="yesterday" --oneline) | \
claude -p "Summarise this cross-repo work for a standup."
Save any of these as a shell alias and you've got a one-command standup generator.
Your commit history knows what you did — Claude just makes it readable.
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.