Agent skill · operations · aiskillstore
chronicle-workflow
Complete workflow for tracking development work with Chronicle - session recording, git tracking, AI summarization, and Obsidian documentation. Works with CLI commands (portable) or MCP tools (faster). Use when starting a new development session, setting up project tracking, or when user wants comprehensive session management.
Why this skill is useful
Adds a complete set of CLI commands and workflows for session tracking and documentation that enhance the AI's capabilities in managing development work.
What it needs
Requires chronicle installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Chronicle Workflow This skill guides you through the complete Chronicle workflow for tracking and documenting development work. Primarily uses CLI commands for portability, with optional MCP tools for faster programmatic access. Auto-Activation This skill auto-activates! (Milestone #13) Prompts like "start a new session" or "is this tracked?" automatically trigger this skill. No manual loading needed! Trigger patterns: start session, is this tracked, chronicle workflow, setup See: docs/HOOKS.md for full details When to Use This Skill Use this skill when: User is starting a new development session Setting up Chronicle for the first time Want to ensure all work is being tracked Need guidance on Chronicle best practices Building a comprehensive development knowledge base Complete Workflow 1. Session Start (If Not Already Tracking) Check if in Chronicle session: Current session is likely NOT being tracked unless started with chronicle start claude To track current work, user must exit and restart with Chronicle Guide user: Important: Chronicle sessions must be started explicitly - they don't auto-track. 2. During Development Best Practices: Work naturally - Chronicle captures everything automatically Make frequent git commits with descriptive messages Chronicle links commits to sessions automatically (±30 min window) Available Commands (don't interrupt work to run these): 3. Session End Automatic on Exit: Full transcript captured to ~/.ai-session/sessions/sessionN.log Metadata saved (duration, timestamp, repo) Session record created in database What happens: 4. Post-Session Documentation Generate Summary (Automatic on first view): Document to Obsidian: Use the chronicle-session-documenter skill or manually: 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/chronicle-workflow