groove-utilities-memory-log-git

Record Git activity summaries into dated Markdown memory log files.

5|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/andreadellacorte/groove --skill groove-utilities-memory-log-git
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: groove-utilities-memory-log-git
Source: https://github.com/andreadellacorte/groove/tree/main/.agents/skills/groove-utilities-memory-log-git
Command: npx skills add https://github.com/andreadellacorte/groove --skill groove-utilities-memory-log-git

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of recording your Git activity, ensuring that your daily progress and code changes are systematically logged for future reference and analysis.

Core Features & Use Cases

  • Automatic Git Summarization: Captures commits made since midnight, current Git status, and diff statistics.
  • Structured Memory Logging: Creates a dated and auto-incremented Markdown file in your memory log for easy retrieval.
  • Use Case: After a coding session, run this skill to automatically generate a summary of your commits and changes, which is then saved to your .groove/memory/git/ directory, ready to be reviewed or included in your daily log.

Quick Start

Use the groove-utilities-memory-log-git skill to record your git activity for today.

Frequently Asked Questions about groove-utilities-memory-log-git

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically log my daily git commit history to a file?

To automatically log your daily git commit history, this skill captures commits made since midnight, current git status, and diff statistics, then saves them into a dated, auto-incremented Markdown memory file.

What is the best way to track code changes from a coding session for daily review?

The best way to track code changes for daily review is to run this skill after a coding session, which generates a summary of your commits and saves it directly to your memory log directory.

Do I need git command-line tools to record my git activity into a memory log?

Yes, you need git command-line tools installed to record your git activity, as the skill relies on them to query your commit history and generate the memory log file.

How does this skill organize git activity summaries chronologically?

The skill organizes git activity summaries chronologically by applying a specific memory file naming convention, creating dated and auto-incremented Markdown files in your git memory directory.

What specific git information is captured when logging code changes to memory?

When logging code changes to memory, the skill captures your commits made since midnight, your current git status, and your diff statistics into a structured Markdown file.

Can I use this skill to generate a git diff summary for my daily workflow?

Yes, you can use this skill to generate a git diff summary for your daily workflow, as it automatically records diff statistics and commit history into a structured memory log file.