juharris/weekly-summary

Weekly Work Summary

Summarize all work done in the last week by gathering information from pull requests authored by the current user. Emphasize why the pull requests are important to the company and why the director, vice presidents, CTO, and CEO at the company should care about the work that was done. Focus on the impact of the work and how it contributes to the company's goals and success.

Check for the current user's Slack messages in the last week with the most reactions or threads they started with many comments to find important work they did that may not be captured in pull requests, such as important discussions or decisions they contributed to.

Also look for pull requests they reviewed or commented on a lot. Look for pull requests they approved or requested changes.

Check the calendar for meetings in the period. Include notable meetings (project syncs, reviews, 1:1s with decisions) as context for what the user worked on, and summarize them alongside PRs and Slack activity.

Write the entire summary in a single markdown code block so that it can easily be copied into another tool.

Discretion with private sources

Summaries are shared with colleagues and leadership, so use discretion when drawing from DMs, private channels, and 1:1 meetings. It's fine to mention projects, themes, outcomes, and collaborators — e.g. "Nick and I discussed improving the token cache" is fine. Don't quote private messages verbatim, and don't attach names to anything negative or sensitive (criticism, conflict, performance, hiring). Keep it at the "what I worked on" level, not the "what was said" level.

Steps

1. Determine the date 7 days ago: date -v-7d +%Y-%m-%d (macOS) or date -d "7 days ago" +%Y-%m-%d (Linux).

2. Search for PRs merged in the last week across all repos:

   gh search prs --author @me --merged-at ">=$DATE" --merged --json repository,title,body,url,mergedAt,number --limit 100
   

3. Search for PRs created in the last week that are still open:

   gh search prs --author @me --created ">=$DATE" --state open --json repository,title,body,url,createdAt,number --limit 100
   

4. Search for issues created in the last week across all repos. Issues capture intent and planning work that doesn't show up as a PR:

   gh search issues --author @me --created ">=$DATE" --json repository,title,body,url,state,createdAt,number --limit 100
   

5. For any PR or issue whose body is empty or truncated in the search results, fetch the full details:

   gh pr view <number> --repo <owner/repo> --json title,body,url,state,mergedAt,createdAt
   gh issue view <number> --repo <owner/repo> --json title,body,url,state,createdAt
   

6. Search for the current user's notable Slack activity using the Slack MCP tools:

   • Use mcp__playground-slack-mcp__get_user_profile to get the current user's Slack user ID.
   • Use mcp__playground-slack-mcp__get_messages to find the user's messages from the period with the most reactions or lengthy threads, focusing on important discussions, decisions, or announcements.
   • Use mcp__playground-slack-mcp__get_reactions to identify which messages received significant engagement.

7. Produce a summary organized by repository with the following structure:

   Period: <start_date> to <today>

   Start with a brief highlights section (3-5 bullets) calling out the most significant accomplishments across all repos and Slack activity.

   For each repository that had PR or issue activity:

   <owner/repo>

   • Merged PRs — list each with title, PR number (linked to URL), and a one-sentence description of what was accomplished based on the PR title and body.
   • Open PRs — list each with title, PR number (linked to URL), and current status.
   • Issues filed — list each issue the user opened in the period with title, issue number (linked to URL), and a one-sentence summary of the problem or proposal.
   • Notable Reviews — list any PRs where the user was a reviewer, especially those they approved or requested changes on, with links and brief descriptions.

   After the repository sections, include a Notable Slack Activity section with:

   • Messages that received many reactions or sparked significant threads
   • Important discussions, decisions, or announcements the user contributed to
   • Brief context on why each was impactful