Menü
Summarize diary entries for a given time period
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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.
Evaluates whether a GitHub repository (tool, library, or framework) is worth adopting for the current project. Use when given a GitHub repo URL to assess as a potential dependency or tool.
Analyzes a GitHub issue by fetching its details and exploring the relevant codebase to identify the root cause and suggest solutions. Use when given a GitHub issue URL to investigate.
Creates a proof of concept implementation. Provides the smallest working solution to validate an idea, with no tests and minimal production concerns.
Proofreads a blog post for clarity, balance, and general quality. Use when asked to proofread, review, or critique a blog post or article.
Review open review comments on a GitHub PR, agree a fix with the user, apply the change, commit, push, and mark the thread resolved.
| name | bms:summarise-diary |
| description | Summarize diary entries for a given time period |
Summarise diary entries for a monthly performance review.
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 for mpc-MM-YYYY.md (e.g., mpc-01-2025.md for January 2025). That file is the output target.
Generate a summary under these headings:
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.
Use markdown. Start with a heading for the month (e.g. # January 2025).
