worklog

Syncs Jira tickets into Obsidian daily journal checklists and writes end-of-day recaps.

1|Updated Aug 6, 2025
One-click install
npx skills add https://github.com/azaidrahman/zaid-sani-dotfiles --skill worklog-azaidrahman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worklog
Source: https://github.com/azaidrahman/zaid-sani-dotfiles/tree/main/dot_claude/skills/worklog
Command: npx skills add https://github.com/azaidrahman/zaid-sani-dotfiles --skill worklog-azaidrahman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a daily work journal in sync with Jira is manual and repetitive: you have to look up your assigned tickets, decide what to focus on, type them into your notes, and remember to recap what actually happened at the end of the day. This Skill automates that bridge between Jira and your Obsidian daily journal. ## Core Features & Use Cases - Day start (/worklog start): Pulls your open Jira issues via the Atlassian MCP, discusses priorities with you, then writes only the agreed focus set as a Professional task checklist in today's Obsidian entry. - Day end (/worklog stop): Refreshes the checklist against current Jira statuses, checks off completed tickets, and appends a short narrative recap plus a next-day look-ahead. - Optional tmux integration: Can create one detached tmux session per focus ticket (via a helper script) and optionally launch a Claude Code instance in each, so you attach straight into a ticket-oriented workspace. - Use Case: You start your morning, run /worklog start, pick three tickets from your Jira backlog in conversation, and find them formatted as linked checklist items in today's journal entry - then at 6pm /worklog stop marks the finished one done and writes a two-sentence recap. ## Quick Start Run /worklog start to pull my open Jira tickets into today's Obsidian journal entry and help me pick today's focus tasks.

Frequently Asked Questions about worklog

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

FAQPage Schema
How do I sync Jira tickets into my Obsidian daily notes?

Run /worklog start to query your open Jira issues via the Atlassian MCP, discuss which ones to focus on, and write the chosen set as a checklist in today's Obsidian journal entry. The checklist uses linked ticket keys with short labels and status names.

How do I generate an end-of-day work recap from Jira?

Run /worklog stop to re-query the tickets in your checklist, mark completed ones as done, and append a narrative recap of at most three sentences plus a next-day look-ahead line. Re-running replaces the existing recap instead of stacking duplicates.

Does this work with any Obsidian vault structure?

It expects a specific layout: entries under 2-Journals/Entry named like 'Wed, 03-06-2026.md', a template at 98-Templates/Journal Template.md, and a '**Professional**' section followed by a '# Meetings' heading. The vault path comes from the OBSIDIAN_VAULT environment variable.

Can I create a tmux session for each Jira ticket automatically?

Yes, after the checklist is written the skill offers an opt-in sync that calls its worklog-tmux-session.sh script per ticket. The script is idempotent, names sessions after the worktree, and can optionally launch a Claude Code instance in each session.

What happens if I run /worklog start twice in one day?

The skill rewrites only its owned region between the '**Professional**' line and the '# Meetings' heading, so re-running never duplicates content. Other sections of the journal entry are never touched.