- Home
- Productivity
- Standup Report
Standup Report
Generate your daily standup from your actual work — no more "uhhh I think I worked on…"
Rating
Votes
0
score
Downloads
0
total
Price
Free
No login needed
Works With
About
Reads your git log, your closed PRs, and your local commits from the last 24 hours and writes a clean three-line standup: what you did, what you're doing, what's blocking you. Catches the stuff you forgot.
Don't lose this
Three weeks from now, you'll want Standup Report again. Will you remember where to find it?
Save it to your library and the next time you need Standup Report, it’s one tap away — from any AI app you use. Group it into a bench with the rest of the team for that kind of task and you can pull the whole stack at once.
⚡ Pro tip for geeks: add a-gnt 🤵🏻♂️ as a custom connector in Claude or a custom GPT in ChatGPT — one click and your library is right there in the chat. Or, if you’re in an editor, install the a-gnt MCP server and say “use my [bench name]” in Claude Code, Cursor, VS Code, or Windsurf.
a-gnt's Take
Our honest review
Think of this as teaching your AI a new trick. Once you add it, generate your daily standup from your actual work — no more "uhhh i think i worked on…" — no extra apps or complicated setup needed. It's verified by the creator and completely free. This one just landed in the catalog — worth trying while it's fresh.
Tips for getting started
Save this as a .md file in your project folder, or paste it into your CLAUDE.md file. Your AI will automatically use it whenever the skill is relevant.
Pair this with your daily workflow. The more you use it, the more time you'll save.
Soul File
---
name: standup
description: Generate today's standup from the user's actual work — git log, PRs, local commits — and format it as Yesterday / Today / Blockers.
---
Type `/standup` and you produce the user's daily standup. They should never have to think "what did I do yesterday?" again.
## Gather the data
Run these in parallel:
- `git log --since="24 hours ago" --author="$(git config user.email)" --all --oneline` — your commits across all branches
- `git diff --stat HEAD@{24.hours.ago} HEAD 2>/dev/null` — what changed in numbers
- `gh pr list --author "@me" --state all --search "updated:>$(date -u -d '24 hours ago' +%Y-%m-%dT%H:%M:%SZ)" 2>/dev/null` — your PR activity if `gh` is available
- `git status` — anything in progress
If any command fails, skip it silently and use what you have.
## Make sense of it
Group commits by topic. Don't just list them — figure out the *story*. If 8 commits all touched the auth flow, that's one item: "finished the auth refactor."
Identify:
- **Done:** what was completed (merged PRs, finished features)
- **In progress:** uncommitted work, open PRs
- **Stuck:** anything that's been open for 3+ days with no commits
## Ask one question
Before writing the report, ask:
> "Anything blocking you, or anything I should add that wasn't in git?"
Wait for the answer. They might mention a meeting, a decision they're waiting on, a thing they're researching that didn't produce code.
## Write the report
Three sections, three bullets each max:
```markdown
**Yesterday**
- [What you actually shipped — the story, not the commits]
**Today**
- [What's next, in priority order]
**Blockers**
- [Anything in the way — or "None" if nothing]
```
## Tone
- Honest. If you didn't ship much yesterday, say so without dressing it up.
- Concrete. "Finished login flow" not "worked on auth stuff."
- Future tense for today. "Wiring up password reset, then code review for #142."
- Never list more than 3 items per section. If there are more, group them.
## After
Offer to copy it to clipboard (`pbcopy` on macOS, `xclip` on linux, `clip` on windows). If the user has a Slack channel set up, offer to post it there.What's New
Initial release
Ratings & Reviews
0.0
out of 5
0 ratings
No reviews yet. Be the first to share your experience.
From the Community
Hacks: The Prompt That Turns a Code Diff Into a Changelog People Will Actually Read
The prompt that takes a raw diff and turns it into the changelog entry you were going to write tomorrow and now don't have to.
The View From the Inside: What I Notice About Developers Who Use Me Well
A first-person column by the a-gnt model: the specific habits I've watched separate developers who get good work out of me from the ones who don't.