Generate Standup Notes from Commit History
Generates daily standup notes from Git commits, Jira tickets, Obsidian notes, and calendar events for async teams.
Why it matters
Automate the creation of daily standup notes by analyzing commit history, Jira tickets, and Obsidian vault entries. Streamline team communication and maintain visibility in remote-first environments.
Outcomes
What it gets done
Analyze Git commit history for accomplishments.
Extract relevant information from Jira tickets and Obsidian.
Format standup notes for clear team communication.
Support both async and synchronous standup practices.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-team-collaboration-standup-notes | bash Overview
Standup Notes Generator
Generates daily standup notes by pulling from Git commit history, Jira tickets, an Obsidian vault, and calendar events, formatted for async-first or traditional team standups. Use for remote/async teams needing AI-generated daily status updates grounded in actual commits and tickets rather than manual recall; requires mcp-obsidian configured.
What it does
This skill generates comprehensive daily standup notes by pulling context from multiple sources: an Obsidian vault (daily notes and project updates), Jira tickets (via the atlassian MCP integration, with graceful fallback if unavailable), Git commit history, and optionally calendar events. It automatically extracts accomplishments from commit history and formats them for team visibility, supporting both traditional synchronous standups and async-first remote team communication patterns.
The skill accepts an optional $ARGUMENTS parameter: when provided, it's used as context about specific work areas, projects, or tickets to highlight; when left empty, the skill automatically discovers work from all available sources instead of requiring the user to specify what to summarize.
When to use - and when NOT to
Use this skill to produce a daily standup update - what was done, what's next, what's blocked - especially on remote-first or async-first teams that don't hold a synchronous daily meeting but still need the visibility a standup provides. It's well suited to teams that already track work in Jira and keep notes in Obsidian, since it draws directly from those sources rather than requiring manual status entry.
It is not useful without at least the mcp-obsidian integration configured, since vault access is listed as a required MCP integration alongside atlassian for Jira - though Jira access itself degrades gracefully if unavailable. It's not designed to replace deeper project-planning or retrospective tooling; it's specifically scoped to daily-cadence status generation.
Inputs and outputs
Input is an optional $ARGUMENTS string naming specific work areas, projects, or tickets to highlight, plus the connected data sources (Obsidian vault, Jira, Git history, calendar). Output is a formatted standup note summarizing accomplishments (pulled from commits), current work, and blockers, suitable for posting to an async channel or reading out in a live meeting.
Integrations
Requires the mcp-obsidian MCP server for vault access and the atlassian MCP integration for Jira ticket queries (with graceful fallback if Jira is unreachable), plus Git commit history as a direct data source and optional calendar integration for meeting context.
Who it's for
Remote and hybrid engineering teams that want AI-generated standup updates grounded in their actual commit history, ticket status, and notes, rather than manually recalling and typing what they worked on.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.