finish-the-day

Files (1)

• SKILL.md

SKILL.md (first lines)

# 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:

```bash
# 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:

```bash
# 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"
```

If no daily updates folder exists, ask the user where to create the log or create `./daily-updates/` in the project root.

### Step 4: Create Daily Update Log

Generate a markdown file with the following structure:

```markdown
# Daily Development Update - [DATE]

## Overview
[Brief summary of what was accomplished]

---

## 1. [Feature/Area Name]

### [Sub-feature]
- Description of changes
- Key implementation details
- Files affected

### Code Changes
[Relevant code snippets or interface definitions]

---

## 2. [Next Feature/Area]
...

From Claude-Code-Community-Ireland/claude-code-resources, MIT.

More from Claude-Code-Community-Ireland/claude-code-resources