log-work
log-work creates timestamped work log entries in a WORKLOG/YYYYMMDD.md file, documenting completed tasks with session IDs, files created or modified, and brief descriptions of work performed. Use this tool to maintain a chronological record of development activities and changes made during coding sessions.
git clone --depth 1 https://github.com/pchalasani/claude-code-tools /tmp/log-work && cp -r /tmp/log-work/plugins/workflow/skills/log-work ~/.claude/skills/log-workSKILL.md
# log-work 1. create the file WORKLOG/YYYYMMDD.md if it doesn't already exist. 2. if the file exists, append a new TOP-LEVEL markdown section to it. 3. When you add a section, follow this format for the section header, so it has HH:MM timestamp followed by suitable concise topic ```markdown # 13:45 Added feature xyz ``` In the log section include a CONCISE set of items such as the following (Not all may apply to all situations, use your judgement): - the session_id of the current session - any text/md file(s) you CREATED and their purpose - any text/md file(s) you READ as part of the current task - short description of what you just did, including any results you got - which code files were created/changed
Extract full context of the last task from the most recent parent session
For CLI agents WITHOUT subagent support (e.g., Codex CLI). Search previous code agent sessions for specific work, decisions, or code patterns.
Use this skill when you learn one or more design pattern(s) in the
Design patterns for the Langroid multi-agent LLM framework. Covers
>-
CLI utility to communicate with other CLI Agents or Scripts in other tmux panes; use it only when user asks you to communicate with other CLI Agents or Scripts in other tmux panes.
This skill should be used when the agent needs to give a spoken voice update to the user, or when reminded by a Stop hook to provide audio feedback. Use this skill to speak a short summary of what was accomplished.
Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.