bms:summarise-diary
Summarise diary entries for a monthly performance review.
Instructions
-
Parse the arguments: $ARGUMENTS should be in format YYYY/MM (e.g., 2025/01). If not fully specified, default to the current year and/or month.
-
Read all files in
diary/YYYY/MM/EXCEPT formpc-MM-YYYY.md(e.g.,mpc-01-2025.mdfor January 2025). That file is the output target. -
Generate a summary under these headings:
- Projects: What I worked on, progress made, blockers encountered
- Team: Collaboration, support given/received, team interactions
- Tech Leads: Work with/for tech leads, technical decisions, architecture discussions
- Department: Broader department initiatives, cross-team work, process improvements
-
Be concise but specific. Include concrete examples and names where they appear in the entries.
-
Save the summary to
diary/YYYY/MM/mpc-MM-YYYY.md(e.g.,diary/2025/01/mpc-01-2025.md). If the file exists, overwrite it.
Output format
Use markdown. Start with a heading lik.
More from benmatselby/dotfiles
git-log-summary
Provides a summary of the git log for the past period of time. Use when asked to provide a git log summary.
18bms:git-log-summary
Provides a summary of the git log for the past period of time. Use when asked to provide a git log summary.
2bms:poc
Creates a proof of concept implementation. Provides the smallest working solution to validate an idea, with no tests and minimal production concerns.
1bms:log-session
Log a one-line summary of the current OpenCode session to today's work diary under the Completed section
1bms:draft-pr
Create a draft pull request for the current branch. Summarises the diff, fills in any PR templates, and opens the PR via the gh CLI.
1bms:code-review
Performs a harsh but constructive code review of a file or set of files. Use when asked to review, critique, or give feedback on code quality.
1