skills.rest
qa-aman
qa-amanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

work-log

Generate daily work logs from Claude Code JSONL session transcripts.

11|Updated Mar 20, 2026
Search Tags:#claude code#activity tracking#daily log#work log#backfill#session transcripts#jsonl parsing
One-click install
npx skills add https://github.com/qa-aman/next-leap-claude-code --skill work-log-qa-aman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work-log
Source: https://github.com/qa-aman/next-leap-claude-code/tree/main/.claude/skills/work-log
Command: npx skills add https://github.com/qa-aman/next-leap-claude-code --skill work-log-qa-aman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Reconstructing what you actually did on a given day is tedious and error-prone when work spans many Claude Code sessions. This Skill reads the project's session transcripts from disk and turns them into an accurate, evidence-based daily work log, including backfilling days that were never logged. ## Core Features & Use Cases - Transcript indexing: Scans every JSONL session transcript for the project, groups activity by IST day, and reports which days already have a log file and which are missing. - Evidence digests: Extracts per-session prompts, files written or edited, git commits, skills and subagents used, todos, and bash commands for any date. - Structured log writing: Writes one Markdown file per day to .local/log/<MM-monthname-YYYY>/ with a summary, task blocks, files changed, evidence, open threads, and a sessions table, with append-safe re-runs. - Use Case: After a week of intense development, run the work log to backfill five missing days and produce a factual record of what shipped each day, grounded in actual session evidence rather than memory. ## Quick Start Ask Claude to run /work-log to generate today's work log and backfill any missing days from this project's session transcripts.

Frequently Asked Questions about work-log

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

FAQPage Schema
How do I generate a daily work log from Claude Code sessions?▼

Run the extract_day.py script with --index to list all dates with session activity, then use --date DD-MM-YYYY to pull an evidence digest for each day. The Skill then writes a structured Markdown log per day into .local/log/.

How do I backfill missing work logs for past days?▼

The --index output lists MISSING_DATES for days with activity but no log file. If more than five days are missing, the Skill asks whether to process all of them, the most recent five, or today only, then backfills each selected date.

Does the work log handle sessions that span midnight?▼

Yes. Transcript timestamps are stored in UTC and the extractor converts everything to IST, so a session running past midnight UTC is split correctly across two day files based on IST dates.

What happens if I run the work log twice on the same day?▼

Re-running is safe because the log writing is append-safe. Existing files are never overwritten; only new task blocks not already recorded are appended, and the header counts and sessions table are updated.

Where are the generated work log files stored?▼

Logs are written to .local/log/<MM-monthname-YYYY>/<DD-MM-YYYY>.md inside the project repository. The .local/ directory is intended to stay out of version control.

Related Skills

Explore More Software Engineering Skills→
tcdenttcdent

get-history-filename

Locate JSONL transcript files for Claude Code and Codex sessions via tmux pane tracing.

Community
Advanced
Clos01Clos01
3

weekly-update

Create structured weekly update slide decks in single-file horizontal HTML format.

Community
Intermediate
basicmachines-cobasicmachines-co
4.0k

bm-remember

Captures quick notes into Basic Memory as Markdown files via MCP.

Official
Intermediate
psw7205psw7205
1

trace-change-why

Traces the rationale behind code changes from session transcripts and git history.

Community
Intermediate