Work Logger

Manual time-tracking and standup prep waste hours every week. This skill automates work logging directly within Claude Code, capturing every edit and session detail without manual entry.

What it does

• Automatic tracking records session start times, end times, and file edits across all projects.
• Turn summaries generates one-line descriptions of each interaction within a session.
• Standup preparation formats daily logs into clean, per-project summaries for easy pasting.
• Manual entries allows logging meetings, blockers, or non-code events via specific commands.
• History filtering retrieves logs for specific dates or projects from the local archive.

How it works

1. Verification checks the current Claude Code environment to see if the plugin is already active.
2. Installation adds the specific GitHub marketplace and installs the plugin via the CLI.
3. Session Refresh triggers the lifecycle hooks by starting a new session to begin recording.
4. Command access uses the /work-logger prefix to query history or add manual context.

Frameworks & tools

This skill works exclusively with Claude Code. It manages a local markdown file, typically located at ~/.claude/daily-log.md.

Why this beats prompting it yourself

Standard prompts cannot access lifecycle hooks like SessionStart or Stop. This skill installs a persistent system plugin that captures metadata and file changes that a generic chat session would lose once the window is closed.

Use cases

• Standup automation by generating a clean list of yesterday's edits and accomplishments.
• Timesheet accuracy by reviewing precise session start and end timestamps across multiple repos.
• Context recovery when returning to a project after several days to see exactly what was last modified.

Known limitations

Requires Claude Code to be installed. Users upgrading from the legacy install.sh script must manually clean up previous versions to avoid duplicate entries.