skills.rest
Yoodaddy0311
Yoodaddy0311COMMUNITY
Explore all skills by this author →
GitHub

session-worklog

Appends structured session work journal entries to a persistent auto-memory markdown file.

3|2|Updated Feb 13, 2026
Search Tags:#workflow#markdown#decision log#context recovery#worklog#auto-memory#session journal
One-click install
npx skills add https://github.com/Yoodaddy0311/artibot --skill session-worklog-yoodaddy0311
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-worklog
Source: https://github.com/Yoodaddy0311/artibot/tree/main/plugins/artibot/skills/session-worklog
Command: npx skills add https://github.com/Yoodaddy0311/artibot --skill session-worklog-yoodaddy0311

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Work context is lost between sessions, forcing you to reconstruct what was done, why decisions were made, and what remains pending. This Skill maintains a lightweight, auto-appended work journal in auto-memory so every new session starts with full recovery context. ## Core Features & Use Cases - Automatic Entry Appending: Triggers on commits, pushes, completed features, session endings, or explicit requests like "log this". - Strict Entry Format: Records tasks, decisions with rationale, and pending items in a fixed markdown structure of roughly 10-15 lines per session. - Size Management: Enforces a 200-line and 10-entry cap by auto-trimming the oldest entries while preserving the file header. - Use Case: After finishing a feature and committing, the Skill appends a dated entry summarizing completed work, key decisions, and blockers, so the next session resumes with full awareness of pending items. ## Quick Start Ask the assistant to log this session's work, decisions, and pending items into the worklog before ending the session.

Frequently Asked Questions about session-worklog

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

FAQPage Schema
How do I keep a work log across Claude Code sessions?▼

Use a session worklog stored in the auto-memory directory at ~/.claude/projects/<project-slug>/memory/worklog.md. Because it lives in auto-memory, it persists across sessions and loads automatically at session start for immediate context recovery.

How to automatically log work after a git commit?▼

Configure an auto-append trigger that fires on commit or push operations, completed features, or session endings. Each trigger appends a concise entry with tasks, decisions, and pending items in a fixed markdown format.

What is the difference between a worklog and git log?▼

A git log shows commit history, while a worklog records decisions, rationale, blockers, and dead-ends that commits do not capture. Worklogs serve as an index to past decisions for future sessions.

When should I not write a worklog entry?▼

Avoid logging mid-task during active problem-solving, since it interrupts flow. Reserve entries for session boundaries, natural breakpoints, completed work blocks, or explicit user requests.

How do I prevent a session log file from growing too large?▼

Enforce a hard cap such as 200 lines and 10 entries, then auto-trim the oldest entry when appending would exceed the limit. Always preserve the file header and keep each entry to roughly 10-15 concise lines.

Related Skills

Explore More Software Engineering Skills→
kangmominkangmomin
1

commit-hd

Organize code changes into logical Git commits with consistent messages.

Community
Intermediate
kks0488kks0488
26

v-continue

Resume work from the latest .vibe/work-*.md state file.

Community
Basic
Heretek-AIHeretek-AI

autonomous-pulse

Automate session maintenance, activity logging, and Git commits for agent pools.

Official
Advanced
mathiasbourgoinmathiasbourgoin
2

git-conventions

Standardize git commit messages, branch names, and pull request descriptions.

Community
Intermediate