# Track Chronicle Development Sessions

Development sessions are hard to reconstruct after commits, tool changes, and context switches. This skill guides Chronicle session tracking, summaries, search, and Obsidian documentation from one workflow.

## Install

```bash
npx skillstore add chandlerhardy/chronicle-workflow
```

## Metadata

- Status: approved
- Slug: chandlerhardy-chronicle-workflow
- Skillstore revision: r1
- Version status: missing
- Tree hash: f927ab11e0730e872062110648d0e8e64e04a461f6481d7834307bc7963532ca
- Author: ChandlerHardy
- GitHub username: ChandlerHardy
- License: MIT
- Repository: https://github.com/ChandlerHardy/chronicle/tree/main/chronicle-skills/chronicle-workflow
- Ref: 02f077c174c5335e2f5d02ca15e77b70d9543e58
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/chandlerhardy-chronicle-workflow
- Manifest: https://skillstore.pages.dev/api/skills/chandlerhardy-chronicle-workflow/manifest

## Capabilities

- Guides users to start Chronicle-tracked AI sessions before development begins.
- Provides Chronicle CLI commands for sessions, timelines, summaries, and search.
- Explains where transcripts, metadata, and the SQLite database are stored locally.
- Describes Obsidian documentation handoff for important sessions.
- Supports multi-project filtering by repository path and recent work retrieval.

## Use Cases

- Start Clean Tracking: Start a Chronicle-tracked Claude, Codex, or Claude Code session before feature work begins.
- Review Recent Work: Use timelines and summaries to understand recent changes, blockers, and follow-up tasks.
- Build Project Memory: Turn important sessions into Obsidian notes with linked repos, commits, and decisions.

## Prompt Templates

### Start a Chronicle Session

```
Help me start a Chronicle-tracked development session for this repository.
```

### Check Tracking Status

```
Check whether this work is tracked by Chronicle and explain what to do next.
```

### Summarize Recent Work

```
Use Chronicle to find my recent work on this project and summarize key decisions.
```

### Plan Project Memory

```
Design a Chronicle workflow for multi-day feature work, including session start, commits, summaries, and Obsidian documentation.
```

## Limitations

- Requires Chronicle to be installed and configured outside the skill.
- Cannot recover full tracking for sessions that were not started through Chronicle.
- Obsidian and MCP workflows require related tools or skills to be available.
- AI summarization may process transcript content through the configured AI provider.

## Best Practices

- Start Chronicle before work begins so transcripts and metadata are complete.
- Commit frequently with clear messages so Chronicle can link sessions to commits.
- Document important sessions in Obsidian after summaries are generated.

## Anti Patterns

- Assuming Chronicle can reconstruct a session that was not started through it.
- Running browse commands during focused development without user intent.
- Treating generated summaries as final records without reviewing key details.

## Security Audit

- Audited at: 2026-07-05T07:17:22.906\+00:00
- Summary: All 46 static findings are documentation false positives caused by Markdown backticks, local Chronicle storage paths, and example retrieval prompts. No evidence found of prompt injection, data exfiltration, unsafe hidden-file access, or executable source code in SKILL.md.

## Stats

- Views: 219
- Downloads: 9
- Favorites: 0
- Popularity score: 0