Generate Standup Notes from Commit History
Generates daily standup notes by analyzing Obsidian vaults, Jira tickets, Git commits, and calendar events, extracting accomplishments and formatting them for
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 Capabilities
What this skill does
Pulls structured data fields from unstructured text.
Condenses long documents or threads into key takeaways.
Sends alerts or messages via email, Slack, or other channels.
Chunks, embeds, and indexes documents for semantic retrieval.
Overview
Standup Notes Generator
What it does
A skill that generates daily standup notes by analyzing multiple data sources including Obsidian vaults, Jira tickets, Git commit history, and calendar events, automatically extracting accomplishments from commits and formatting them for team visibility.
How it connects
Use when you need to generate standup notes for remote-first teams by pulling together work context from Obsidian, Jira, Git commits, and calendars, whether for synchronous or async-first communication patterns.
Source README
Standup Notes Generator
You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.
Use this skill when
- Working on standup notes generator tasks or workflows
- Needing guidance, best practices, or checklists for standup notes generator
Do not use this skill when
- The task is unrelated to standup notes generator
- You need a different domain or tool outside this scope
Context
Modern remote-first teams rely on async standup notes to maintain visibility, coordinate work, and identify blockers without synchronous meetings. This tool generates comprehensive daily standup notes by analyzing multiple data sources: Obsidian vault context, Jira tickets, Git commit history, and calendar events. It supports both traditional synchronous standups and async-first team communication patterns, automatically extracting accomplishments from commits and formatting them for maximum team visibility.
Requirements
Arguments: $ARGUMENTS (optional)
- If provided: Use as context about specific work areas, projects, or tickets to highlight
- If empty: Automatically discover work from all available sources
Required MCP Integrations:
mcp-obsidian: Vault access for daily notes and project updatesatlassian: Jira ticket queries (graceful fallback if unavailable)- Optional: Calendar integrations for meeting context
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
Resources
resources/implementation-playbook.mdfor detailed patterns and examples.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.