From skills
Generates a casual daily standup from git activity in the last 24 hours, translating commit messages into human-readable accomplishments.
How this skill is triggered — by the user, by Claude, or both
Slash command
/skills:standupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Transform git history into a human standup update. Nobody cares about commit
Transform git history into a human standup update. Nobody cares about commit messages — translate them into what you actually accomplished.
git log --since="24 hours ago" --author="$(git config user.email)" --oneline
If multiple repos are relevant, run in each. If no commits: skip to Step 3.
Map raw commit messages → casual language. The rule: write what you'd say out loud to a teammate, not what you typed in the terminal.
| Raw commit | Translated |
|---|---|
feat(modal): add purchase modal skeleton | Shipped the purchase modal skeleton |
fix: resolve pagination bug | Finally got that pagination bug squashed |
refactor: migrate to React Query | Got the React Query migration working |
chore: update dependencies | Bumped deps (skip — not worth a bullet) |
docs: update README | Updated the README (skip unless it's notable) |
Rules:
If no commits in 24h, say:
Yesterday I:
- Focused on code reviews and planning
Never invent fake accomplishments. Don't mention the absence of commits.
In order of preference:
git branch --show-current → parse intent
feat/payment-flow → "Continue the payment flow"fix/auth-timeout → "Fix the auth timeout issue"Yesterday I:
- [Accomplishment — active verb, specific]
- [Accomplishment 2]
Today I plan to:
- [Inferred from branch or asked]
Blockers: [None, or specific blocker if mentioned]
Omit Blockers line if there are none.
npx claudepluginhub kriscard/skillsGenerates standup summaries from git history, track progress files, and Jira/GitHub activity. Read-only — useful for daily or weekly developer standups.
Generates standup updates summarizing recent commits, PRs, ticket changes, and activity into yesterday/today/blockers format. Works with connected source control/project tools or standalone notes.
Guides writing a polished client update by gathering git context, identifying accomplishments, next steps, and surfacing risks.