standup

Generate daily standup summaries from git log, pull requests, and uncommitted changes.

23|4|Updated Sep 5, 2013
One-click install
npx skills add https://github.com/drn/dots --skill standup-drn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: standup
Source: https://github.com/drn/dots/tree/main/agents/skills/standup
Command: npx skills add https://github.com/drn/dots --skill standup-drn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of daily standup summaries by consolidating recent git activity, commit history, open pull requests, and current work in progress.

Core Features & Use Cases

  • Summarize Git Activity: Quickly generate a concise overview of your recent code changes.
  • Track Open PRs: Keep track of pull requests that require attention.
  • Identify Uncommitted Changes: See what you're currently working on.
  • Use Case: Prepare for your daily team standup meeting by having a ready-made summary of your contributions and ongoing tasks.

Quick Start

Generate a standup summary for the team for the last 3 days.

Frequently Asked Questions about standup

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

FAQPage Schema
How do I generate a daily standup summary from git activity?

You can generate a standup summary for a custom time range by filtering the git log activity and open pull requests. This allows you to easily prepare reports covering specific days or development sprints.

Can I filter git log activity by author for a standup report?

Yes, you can filter the generated standup summary by author. This isolates specific git log activity, open pull requests, and uncommitted changes to report on individual developer contributions.

Do I need the GitHub CLI to track open pull requests in my standup summary?

Yes, tracking open pull requests requires the GitHub CLI. The standup summary integrates with GitHub CLI to fetch PR information, while using git to analyze local commit history and branch status.

What is the best way to track uncommitted changes before a standup?

The best way to track uncommitted changes is using an automated summary tool that analyzes current branch status. It identifies uncommitted changes alongside recent git activity to report work in progress.

Does the standup summary report include current branch status?

Yes, the standup summary includes context on current branch status. It analyzes uncommitted changes and recent git log activity to provide a complete picture of ongoing development tasks.