Branches touched: git branch --sort=-committerdate --format="%(refname:short) %(committerdate:relative)" | head -10
If multiple repos, offer to scan them.
Summarize into standup format.
Output Format
## Standup — YYYY-MM-DD
### Yesterday
- Worked on <feature/area>: <concise summary of commits>
- Fixed <bug>: <summary>
### Today
- Plan to continue <work in progress>
- [Suggested based on open branches and recent context]
### Blockers
- [Any merge conflicts, failing CI, or stale PRs detected]
Guidelines
Group related commits into logical work items rather than listing each commit.
Use natural language, not commit hashes.
Keep it concise — a real standup is 30 seconds.
If gh CLI is available, include open PRs authored by the user.
Detect and mention any unfinished work (branches with no PR, uncommitted stashes).
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: maggit-claude-workspace-standup3description: Standup Report Generator4---56# Standup Report Generator78Generate a concise standup report from recent git activity.910## Workflow11121. Identify the user:13 - `git config user.name` and `git config user.email`.142. Determine the time range:15 - Default: since last business day (skip weekends).16 - Monday → since Friday.17 - Other days → since yesterday.18 - Allow user override (e.g., "last 3 days", "this week").193. Gather activity:20 - Commits: `git log --author="<email>" --since="<date>" --pretty=format:"%h %s (%ar)" --all`21 - Branches touched: `git branch --sort=-committerdate --format="%(refname:short) %(committerdate:relative)" | head -10`22 - If multiple repos, offer to scan them.234. Summarize into standup format.2425## Output Format2627```markdown28## Standup — YYYY-MM-DD2930### Yesterday31- Worked on <feature/area>: <concise summary of commits>32- Fixed <bug>: <summary>3334### Today35- Plan to continue <work in progress>36- [Suggested based on open branches and recent context]3738### Blockers39- [Any merge conflicts, failing CI, or stale PRs detected]40```4142## Guidelines4344- Group related commits into logical work items rather than listing each commit.45- Use natural language, not commit hashes.46- Keep it concise — a real standup is 30 seconds.47- If `gh` CLI is available, include open PRs authored by the user.48- Detect and mention any unfinished work (branches with no PR, uncommitted stashes).4950---51> Converted and distributed by [TomeVault](https://tomevault.io/claim/maggit) — claim your Tome and manage your conversions.52<!-- tomevault:4.0:skill_md:2026-04-15 -->
Run npx skillmds@latest add tomevault-io/maggit-claude-workspace-standup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Standup Report Generator It is listed under Docs & Writing on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.
tomevault-io