standup

Generates standup and sprint updates from git commits, branches, PRs, and task files.

15|3|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/kiurakku/cursor-kit-for-ai --skill standup-kiurakku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: standup
Source: https://github.com/kiurakku/cursor-kit-for-ai/tree/main/plugins/engineering/skills/standup
Command: npx skills add https://github.com/kiurakku/cursor-kit-for-ai --skill standup-kiurakku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing standup updates from memory leads to vague, inaccurate status reports. This Skill pulls real activity from git history, branches, open PRs, and task files, then compresses it into the concise format teammates actually need. ## Core Features & Use Cases - Evidence-Based Gathering: Runs git log, branch listing, git status, and gh pr list commands to collect real activity instead of relying on memory. - Transform Rules: Groups commits by outcome, leads with shipped work, drops noise like merge commits and lockfile churn, and makes blockers actionable. - Multiple Output Variants: Supports daily standup, weekly/sprint summaries with highlights and metrics, async Slack updates, and manager 1:1 prep with a decisions section. - Use Case: Before your morning standup, run this Skill to turn yesterday's eight scattered commits on an auth feature into one clear line — "Finished JWT refresh flow" — plus today's concrete plan and any blockers. ## Quick Start Ask the AI to generate my standup update from yesterday's git activity and open PRs.

Frequently Asked Questions about standup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a standup update from git commits?▼

Run git log with --since="yesterday" and your author email to list recent commits, then group them by outcome rather than listing each commit. The Skill also checks branches, uncommitted work, and open PRs to build a complete picture.

How to write a weekly sprint summary from git history?▼

Use git log with --since="1 week ago" to gather the week's commits, then apply the same grouping rules as a daily standup. Add a Highlights line at the top and a metric such as PRs merged or issues closed.

Does the standup generator work with GitHub pull requests?▼

Yes, it runs gh pr list --author "@me" --state open when the GitHub CLI is available to include open PRs in the update. If gh is not installed, the Skill silently skips that step and relies on git data alone.

What makes a good standup update versus a bad one?▼

Good updates group commits by outcome, lead with shipped work, and state blockers with the specific person or decision needed. Avoid listing commit hashes, branch names, or vague items like "continue working on X" — each Today item should be verifiable tomorrow.

What should I report on days with no commits?▼

Report the day honestly rather than inventing activity. If you context-switched to code reviews or support work, say so explicitly; an empty git log with fabricated progress undermines trust in the update.