end_of_day

Consolidates today's sessions, Git activity and unfinished tasks into a daily cache file.

2|1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/FourthWiz/claude_dev_workflow --skill end-of-day
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: end_of_day
Source: https://github.com/FourthWiz/claude_dev_workflow/tree/main/dev-workflow/skills/end_of_day
Command: npx skills add https://github.com/FourthWiz/claude_dev_workflow --skill end-of-day

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents loss of context and forgotten decisions by aggregating the day's work, unfinished tasks, blockers, and recent Git activity into a reusable daily cache.

Core Features & Use Cases

  • Session aggregation: Reads all session markdown files for the current day and extracts unfinished work and decisions.
  • Git activity summary: Updates a rolling log of recent commits across all repositories.
  • Daily cache generation: Creates a concise daily summary including cost data, insights promotion, and next‑day priorities.
  • Insight promotion & pruning: Filters, deduplicates, and optionally prunes lessons‑learned entries to keep knowledge base lean.

Quick Start

Run the end_of_day skill to consolidate today’s work into a daily cache for tomorrow’s start.

Frequently Asked Questions about end_of_day

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

FAQPage Schema
How do I consolidate daily git activity and session notes for tomorrow?

To consolidate daily git activity and session notes, this Skill aggregates session markdowns and recent commits into a daily cache, preserving unfinished tasks and decisions for seamless resumption.

What is a daily workflow cache and when do I need it?

A daily workflow cache is a consolidated summary of the day's work, blockers, and git activity. You need it to prevent context loss and forgotten decisions when resuming development the next day.

Does the daily session aggregation require specific memory files?

Yes, daily session aggregation requires access to .workflow_artifacts memory files, session markdowns, and git logs to accurately generate summaries and next-day priorities.

What's the best way to capture unfinished tasks and blockers before ending work?

The best way to capture unfinished tasks and blockers is running an end-of-day consolidation that reads session files and git logs to extract pending work into a reusable cache.

Can I prune lessons-learned entries during the daily workflow summary?

Yes, the daily workflow summary includes insight promotion and pruning, which filters, deduplicates, and optionally prunes lessons-learned entries to keep your knowledge base lean.