standup

To generate a daily standup report from git commits and GitHub activity, the skill pulls recent commits, open PRs, and assigned issues using a consistent "since yesterday" time window. It synthesizes this data to infer completed work and planned tasks, formatting the output into Yesterday, Today, and Blockers sections.

Yes, you can use open GitHub PRs and issues to draft your standup. The skill synthesizes recent commits plus your open GitHub activity to infer what you did since yesterday and what you plan to do today, ensuring your daily updates accurately reflect your engineering workflow.

The best way to include blockers and incomplete dependencies in engineering status reporting is to surface them early in a dedicated Blockers section. The skill encourages blocker-first honesty by integrating incomplete work and dependencies directly into the generated daily standup report.

A time-windowed git history summary improves daily updates by using a consistent "since yesterday" window from git and GitHub timestamps. This avoids subjective reporting and provides an accurate snapshot of recent engineering work for routine team check-ins.

No, you do not need to manually hunt through git logs to prepare a routine check-in update. The skill turns raw git history and open GitHub activity into a clear daily standup report, allowing teams to quickly understand progress, plans, and blockers without manual status hunting.