finish-the-day

finish-the-day is a skill for Claude Code from Claude-Code-Community-Ireland/claude-code-resources. It costs 55 tokens per session (1,561 once invoked), scanned A, original, MIT.

An end-of-day workflow that reviews the day’s work, writes a detailed update, commits changes, and pushes them to a remote Git repository.

In plain words
What is it for?
Summarising commits and file changes, documenting decisions, creating a conventional commit, and pushing the result to the remote repository.
Why use it?
It helps turn unfinished work into a recorded, shareable update while keeping the repository synchronised.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is ls -d ../Daily-updates 2>/dev/null || \.

Part of the vibeworks-library plugin — 34 skills, 21 commands, 33 agents, 3 hooks shipped together

Good fit Summarising commits and file changes, documenting decisions, creating a conventional commit, and pushing the result to the remote repository.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/Claude-Code-Community-Ireland/claude-code-resources
agentmods
npx agentmods add skills/claude-code-community-ireland/claude-code-resources/finish-the-day

Made for: Claude Code.

Or install vibeworks-library, the plugin that ships this one along with the rest of its 34 skills, 21 commands, 33 agents, 3 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for finish-the-day

README.md
[![agentmods](https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/finish-the-day/github.svg)](https://agentmods.dev/skills/claude-code-community-ireland/claude-code-resources/finish-the-day)
Your own site
<a href="https://agentmods.dev/skills/claude-code-community-ireland/claude-code-resources/finish-the-day"><img src="https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/finish-the-day/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for finish-the-day

Your own site · 80×15
<a href="https://agentmods.dev/skills/claude-code-community-ireland/claude-code-resources/finish-the-day"><img src="https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/finish-the-day.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,561 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.01561
Opus 5.5 $0.00022 $0.00624
Sonnet 5.5 $0.00011 $0.00312
Haiku 4.5 $0.00006 $0.00156

Measured 1mo ago against content hash d507e5e26088, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

finish-the-day scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/vibeworks-library/skills/finish-the-day/SKILL.md · 255 lines

How it starts

The opening of the file, as written. The whole thing — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Finish the Day - Universal End-of-Day Wrap Up

This skill performs a comprehensive end-of-day wrap up for the current working directory. It analyzes all work done, creates a detailed log, commits changes, and pushes to the remote repository. Works on any project.

What This Skill Does

  1. Analyze Today's Work

    • Reviews all commits made today
    • Identifies all modified, added, and deleted files
    • Calculates lines added/removed
    • Summarizes changes by category
  2. Create Daily Update Log

    • Generates comprehensive markdown documentation
    • Organized by feature/area of work
    • Includes code snippets for key changes
    • Documents technical decisions and notes
  3. Commit All Changes

    • Stages all uncommitted changes
    • Creates detailed commit message
    • Follows conventional commit format
  4. Push to Remote

    • Pushes all commits to remote repository
    • Reports sync status

Execution Steps

Step 1: Gather Information

Collect all data about today's work:

# Get today's date
date +%Y-%m-%d

# Get project name from current directory or package.json
basename $(pwd)

# Check git status for uncommitted changes
git status

# Get diff stats for uncommitted changes
git diff --stat

# Get today's commits (commits from today)
git log --since="midnight" --oneline

# Get detailed changes from today's commits
git log --since="midnight" --stat

# Get all files changed today (committed + uncommitted)
git diff --name-only HEAD~10 2>/dev/null || git diff --name-only

# Count lines changed
git diff --shortstat

Step 2: Analyze Changes

For each changed file:

  1. Read the file to understand what was implemented
  2. Categorize changes by type:
    • New features
    • Bug fixes
    • Refactoring
    • Documentation
    • Configuration
    • Tests
  3. Identify key components created or modified
  4. Note any breaking changes

Step 3: Determine Daily Updates Location

Check for existing daily updates folder:

# Common locations to check (in order of preference)
# 1. Daily-updates in parent directory (for monorepos)
# 2. docs/daily-updates in project
# 3. daily-updates in project root
# 4. Create in project root if none exist

ls -d ../Daily-updates 2>/dev/null || \
ls -d ./docs/daily-updates 2>/dev/null || \
ls -d ./daily-updates 2>/dev/null || \
echo "Will create ./daily-updates"

Read the full file on GitHub · 255 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 255 lines · 55 tokens per session scan A d507e5e26088

Subscribe to this mod's changes

finish-the-day is a skill published in the GitHub repository Claude-Code-Community-Ireland/claude-code-resources (11 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 1,561 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.