Skip to main content
skill CX Codex

groove-utilities-memory-log-daily — Claude Code skill: daily memory

Writes the end-of-day entry to .groove/memory/daily/YYYY-MM-DD.md: what got done, which commits landed, what carries over.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add andreadellacorte/groove --skill groove-utilities-memory-log-daily -a claude-code
Open on GitHub

What groove-utilities-memory-log-daily does

Run this skill when the workday ends. It creates or appends .groove/memory/daily/YYYY-MM-DD.md with closeout sections: Done today, Git, Tasks, Learnings and Open/Next. If the file already exists from the morning start, the skill appends instead of overwriting, so the next daily start can confirm yesterday had an end.

The Done today section comes from completed tasks matched by date plus git diff output, never from unfinished work. A finished task with no resolution in its body triggers a question before anything is written. Vague phrasing gets the same treatment. File structure follows the template at skills/groove-utilities-memory-log-daily/templates/daily.md, and the .groove/memory/daily/ directory is created if missing.

One detail worth knowing: when .groove/.cache/pending-capture.md exists, staged by the session-capture hook, the skill pre-fills Done today and Git from it. You review and edit a draft instead of starting blank. The cache file is deleted once the log is written. This is an end-of-day tool only — calling it at daily start goes against how it works.

What it helps with

  • record what actually shipped today, not what was planned
  • summarise commits and changed files without retyping them
  • carry unfinished tasks into tomorrow
  • capture learnings before they fade
  • append a closeout to a file the morning start already created

Example prompts for the agent

  • Write today's daily memory log entry
  • Close out the day: pull commits and finished tasks into .groove/memory/daily/
  • Append today's summary to the daily log file

How to install groove-utilities-memory-log-daily

1Skills CLI (Vercel)

npx skills add andreadellacorte/groove --skill groove-utilities-memory-log-daily -a claude-code

2Manually: put the files in place

~/.claude/skills/groove-utilities-memory-log-daily/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/groove-utilities-memory-log-daily/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about groove-utilities-memory-log-daily

How do I install groove-utilities-memory-log-daily in Claude?

Run npx skills add andreadellacorte/groove --skill groove-utilities-memory-log-daily -a claude-code. The skill then lives at ~/.claude/skills/groove-utilities-memory-log-daily/SKILL.md.

What does groove-utilities-memory-log-daily do?

It creates or updates .groove/memory/daily/YYYY-MM-DD.md with a structured end-of-day entry: completed tasks, commits, task status, learnings and carry-forward items.

Where does the Done today section get its content?

From date-matched completed tasks and git diff output. If .groove/.cache/pending-capture.md from the session-capture hook is present, the skill drafts those sections from it first.

Source text

SKILL.md · MIT
---
name: groove-utilities-memory-log-daily
description: "Write the daily memory log entry. Use at end of day to record what happened."
license: MIT
allowed-tools: Read Write Edit Glob Grep Bash(git:*) AskUserQuestion
metadata:
  author: andreadellacorte
---

# 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

© andreadellacorte · MIT · andreadellacorte/groove

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set13

groove-utilities-task-analyse Pulls tasks from your project backend and groups them by status, so you have something to write into daily memory. CX Codex +1 588installs groove-utilities-task-list Pulls active tasks from your configured backend and shows what is in progress, ready or blocked. Handy as a daily starting view. CX Codex +1 577installs groove-daily-start Prepares the workday: reviews recent days, creates today's memory file, loads tasks and lays out the agenda. CX Codex +1 571installs groove-work-plan Researches your codebase and writes a concrete implementation plan with ordered steps, file paths and function names. Meant to run after brainstorming. CX Codex +1 544installs groove-work-compound This skill documents lessons after a review or planning session, updates project rules and templates, and traces root causes of mistakes. CX Codex +1 540installs groove-work-exec This skill takes a finished implementation plan and writes the code, tests and docs for it, logging progress in your task backend. Use it once planning is done. CX Codex +1 536installs groove-admin-update Pulls the latest groove skills and applies pending migrations to your local groove state. Useful when a new release lands but your config and memory are still on the old one. CX Codex +1 528installs groove-admin-cursor-hooks Registers groove's native Cursor hooks in .cursor/hooks.json: context re-priming after compaction, end-of-day reminders, a git commit buffer and managed-path protection. CX Codex +1 518installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor