mcpField
G
groove-utilities-memory-log-daily

groove-utilities-memory-log-daily

github.com/andreadellacorteProductivity6581 installsUpdated 14w ago
Repository

About groove-utilities-memory-log-daily

A workflow skill for creating or updating Groove’s end-of-day log from completed tasks and Git changes. It preserves an existing daily-start file and can use pending session-capture data as a draft.

Key features

  1. 01Structured daily closeout sections
  2. 02Sources completed tasks and git diff
  3. 03Summarizes commits and changed files
  4. 04Carries forward open items
  5. 05Uses and removes pending capture

Use cases

  1. 01Writing a daily log from completed work
  2. 02Appending closeout to an existing daily file
  3. 03Reviewing a session-capture draft before saving

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/andreadellacorte/groove --skill groove-utilities-memory-log-daily

After installing, type/groove-utilities-memory-log-dailyin Claude Code to confirm it loaded.

Bundled filestemplates/daily.md

Details

From the project README

groove-utilities-memory-log-daily

Outcome

.groove/memory/daily/YYYY-MM-DD.md is created or updated with a structured end entry. The file may already exist from daily start (start-of-day structure); if so, append the closeout sections. The file is written so that the next daily start can verify yesterday had an end.

Acceptance Criteria

  • File exists at .groove/memory/daily/YYYY-MM-DD.md after command completes
  • "Done today" section contains granular multi-level bullets sourced from completed tasks and git diff
  • Git section summarises commits and changed files for the day
  • Tasks section shows task summary by status
  • Learnings section is populated (not blank)
  • Open/Next section captures carry-forward items
  • If file already exists, content is updated/appended rather than overwritten

Constraints

  • Memory path is always .groove/memory/
  • Write at daily end only — never called at daily start. File may already exist from daily start; append closeout sections rather than overwriting.
  • "Done today" must be sourced from: completed tasks (date-matched) and git diff output — not from incomplete work
  • Pending capture: if .groove/.cache/pending-capture.md exists (staged by the session-capture Stop hook), use it to pre-fill the "Done today" and "Git" sections — its commits/working-changes are the raw material, so the user reviews and edits a draft rather than starting blank. After the daily log is written successfully, delete .groove/.cache/pending-capture.md.
  • If a completed task has no resolution in its body, ask user for a summary before writing the bullet
  • Use template at skills/groove-utilities-memory-log-daily/templates/daily.md for file structure
  • If the directory .groove/memory/daily/ does not exist, create it before writing
  • Vague entries ("worked on stuff") should trigger a clarification ask before writing

Comments

Markdown supported