standup

Summarize git history, brag-book entries, and worktrees into a standup report.

2|1|Updated Oct 8, 2009
One-click install
npx skills add https://github.com/riethmayer/dotfiles --skill standup-riethmayer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: standup
Source: https://github.com/riethmayer/dotfiles/tree/main/stow/agents/.agents/skills/standup
Command: npx skills add https://github.com/riethmayer/dotfiles --skill standup-riethmayer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually compiling standup updates from multiple repositories is time-consuming and error-prone. This skill automates gathering recent development activity from several sources to produce a concise standup summary.

Core Features & Use Cases

  • Aggregates git activity across EagleEye worktrees, standalone repos, and brag-book entries to build a comprehensive daily update.
  • Groups updates by workstream and includes context beyond raw commits, such as notable decisions and debugging sessions.
  • Outputs the standup to an Obsidian daily note, keeping your journal consistent and searchable.

Quick Start

Generate today's standup notes from recent activity and write them into your Obsidian daily note.

Frequently Asked Questions about standup

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

FAQPage Schema
How do I generate daily standup notes from git history?

Generate daily standup notes from git history by aggregating recent commits across worktrees and standalone repositories. The skill filters out noise and groups updates into a concise narrative by workstream for your daily notes.

Can I aggregate git activity from multiple worktrees into one update?

Yes, you can aggregate git activity from multiple EagleEye worktrees and standalone repos into one update. The skill consolidates commits and brag-book entries into a single narrative grouped by workstream.

Does this work with Obsidian daily notes?

This works directly with Obsidian daily notes by outputting the generated standup summary into your journal. It keeps your daily notes consistent and searchable without manual copy-pasting.

What's the best way to automate standup updates from multiple repositories?

The best way to automate standup updates from multiple repositories is using a tool that reads git history and brag-book data to filter noise and group activity by workstream. This produces a concise narrative automatically.

Do I need a brag-book to generate a standup report?

A brag-book is not strictly required but enriches the standup report with context beyond raw commits. The skill reads brag-book entries alongside git history to include notable decisions and debugging sessions in the output.

Why does my standup report include irrelevant commits?

Irrelevant commits often appear when manual compilation lacks noise filtering. This skill reads git history and automatically filters out noise, ensuring only meaningful updates grouped by workstream appear in the final report.