feat: add Daily Standup Report Generator recipe (#5123)

[ARYPROGRAMMER]

Summary

Advanced daily standup report generator that automatically fetches GitHub activity (PRs, issues, commits, reviews) and generates professional team standup reports with blocker detection and progress tracking.

Key Features:

• 3 Extensions Used: Developer (file operations), GitHub MCP (API integration), Memory (progress tracking)
• 7 Customizable Parameters: github_owner, github_repo, time_period, include_prs, include_issues, output_format, team_channel
• Multi-Format Output: Markdown, JSON, Slack, Plain Text reports
• Comprehensive Activity Tracking: Merged PRs, open PRs, closed issues, active issues, commits, reviews
• Intelligent Blocker Detection: Identifies failing CI/CD checks, merge conflicts, required reviews, stale PRs
• User-Scoped Filtering: Automatically filters by authenticated GitHub user (author, assignee, reviewer)
• No Local Repo Required: Works entirely via GitHub API, no git commands needed
• Memory Integration: Tracks previous standups for progress continuity
• Guaranteed File Output: Always creates standup-report-{date}.{format} file
• Flexible Time Periods: Supports 24h (default), 7d, 48h, or custom durations
• 6-Phase Workflow: Context → PR Fetching → Issue Fetching → Analysis → Generation → Storage

Type of Change

• Feature
• Bug fix
• Refactor / Code quality
• Performance improvement
• Documentation
• Tests
• Security fix
• Build / Release
• Other

Testing

Setup Required:

# Set GitHub personal access token
export GITHUB_PERSONAL_ACCESS_TOKEN="your-github-token"

Ref: https://block.github.io/goose/docs/mcp/github-mcp

Primary Test:

goose run --recipe documentation/src/pages/recipes/data/recipes/daily-standup-report-generator.yaml --params github_owner=ARYPROGRAMMER --params github_repo=goose --params time_period=24h

Additional Tests:

# Weekly report with issues
goose run --recipe documentation/src/pages/recipes/data/recipes/daily-standup-report-generator.yaml --params github_owner=ARYPROGRAMMER --params github_repo=goose --params time_period=7d --params include_issues=true

# Slack format output
goose run --recipe documentation/src/pages/recipes/data/recipes/daily-standup-report-generator.yaml --params github_owner=ARYPROGRAMMER --params github_repo=goose --params time_period=24h --params output_format=slack

# JSON format for automation
goose run --recipe documentation/src/pages/recipes/data/recipes/daily-standup-report-generator.yaml --params github_owner=block --params github_repo=goose --params time_period=24h --params output_format=json

Screenshot:

Expected Output:

• Standup report file created at ./standup-report-{YYYY-MM-DD}.{format}
• Sections: Completed, Open PRs, Active Issues, Next Steps, Blockers
• GitHub data filtering by authenticated user
• Blocker detection from PR reviews, CI/CD failures, merge conflicts

Related Issues

Fixes #5123

Email: [email protected]

[github-actions]

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

1. Our team will review your recipe
2. If approved, we'll run a security scan
3. Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

[github-actions]

🔍 Recipe Security Scan Results

✅ Status: APPROVED - All recipes passed security scan

📊 Scan Summary:

• Total recipes scanned: 1

📋 Individual Recipe Results:
✅ Recipe 1: APPROVED (LOW risk)

🔗 View detailed scan results in the workflow artifacts.

[iandouglas]

Great use of github to summarize a team's workload and status. As with other recipes where I've left reviews, the memory extension is best used for short general-purpose things like "remember when writing anything about goose, always lowercase the word goose unless starting a sentence" or "when I want code in Python, use 3.14" etc., as those get sent with every LLM request that goose sends from the user. Overloading your goose memory extension with extensive notes and summaries of code, documentation styles, or standup meetings will send a lot of unnecessary context to the LLM when requesting unrelated work.

[ARYPROGRAMMER]

resolved all

[ARYPROGRAMMER]

Great use of github to summarize a team's workload and status. As with other recipes where I've left reviews, the memory extension is best used for short general-purpose things like "remember when writing anything about goose, always lowercase the word goose unless starting a sentence" or "when I want code in Python, use 3.14" etc., as those get sent with every LLM request that goose sends from the user. Overloading your goose memory extension with extensive notes and summaries of code, documentation styles, or standup meetings will send a lot of unnecessary context to the LLM when requesting unrelated work.

my eventual thought is can we create a custom extension for this particular kind of storing everytime. maybe use the logs to keep a track if needed. just a thought because then LONGER CONTEXT storage would be beneficial at a lot of places

[github-actions]

✅ Recipe Validation Passed

Your recipe(s) are valid and ready for review!

🔍 Next Steps:

1. Our team will review your recipe
2. If approved, we'll run a security scan
3. Once merged, you'll receive $10 in OpenRouter credits (if email provided)

Thanks for contributing to the goose Recipe Cookbook! 🎉

[github-actions]

🔍 Recipe Security Scan Results

✅ Status: APPROVED - All recipes passed security scan

📊 Scan Summary:

• Total recipes scanned: 1

📋 Individual Recipe Results:
✅ Recipe 1: APPROVED (LOW risk)

🔗 View detailed scan results in the workflow artifacts.

[ARYPROGRAMMER]

this as well is ready for review and merging. i have removed mem extension and resolved all queries

[ARYPROGRAMMER]

any updates? seems good in my double check

addressed