call-it-a-day

Collect session context, summarize changes, and save memory to the memory store.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Rheinmir/skills-kit --skill call-it-a-day
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: call-it-a-day
Source: https://github.com/Rheinmir/skills-kit/tree/main/skills/call-it-a-day
Command: npx skills add https://github.com/Rheinmir/skills-kit --skill call-it-a-day

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you close a work session by automatically collecting current context, summarizing progress, saving memory, and preparing for shutdown.

Core Features & Use Cases

  • Collects recent changes by reading CHANGES.md or CHANGELOG.md when present; if absent, creates a new changelog entry.
  • Runs git commands like git log --oneline -10, git status --short, and optionally compares with origin/HEAD to highlight unpushed commits.
  • Writes context and memory to a persistent memory store to enable seamless resumption in the next session.

Quick Start

Collect the current session context, summarize changes, and save memory to the memory store to prepare for shutdown.

Frequently Asked Questions about call-it-a-day

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

FAQPage Schema
How do I wrap up a git work session and save context for later?

You can wrap up a work session by collecting context and saving memory. This skill reads CHANGES.md, runs git log and git status to capture recent activity, and writes a summary to a persistent memory store for later resumption.

How does saving session memory work when preparing for shutdown?

Saving session memory works by generating a concise status of recent changes and writing it to a persistent memory store. This captures your development context before shutdown, enabling seamless resumption in the next session.

Can I use this to capture unpushed git commits before ending my session?

Yes, you can capture unpushed git commits before ending your session. The skill compares your local repository with origin/HEAD and highlights unpushed commits alongside recent activity in the final memory summary.

Does the workflow require an existing CHANGES.md or CHANGELOG.md file?

The workflow does not require an existing CHANGES.md or CHANGELOG.md file. It reads these files when present to collect recent changes, and automatically creates a new changelog entry if they are absent.

What is the best way to generate a concise status from recent git activity?

The best way to generate a concise status from recent git activity is to automate context collection. This skill runs git log --oneline and git status --short to summarize progress and prepare for shutdown.