# Document AI Development Sessions

Development sessions are hard to review when details stay in chat history or local logs. This skill turns Chronicle data into structured Obsidian notes with summaries, metadata, and links.

## Install

```bash
npx skillstore add chandlerhardy/chronicle-session-documenter
```

## Metadata

- Status: approved
- Slug: chandlerhardy-chronicle-session-documenter
- Skillstore revision: r1
- Version status: missing
- Tree hash: e9e70d1baea80b80b684cc63f54cf032a3473cd23e015fcd2c8d49f03d5950e6
- Author: ChandlerHardy
- GitHub username: ChandlerHardy
- License: MIT
- Repository: https://github.com/ChandlerHardy/chronicle/tree/main/chronicle-skills/chronicle-session-documenter
- 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: 70
- Public page: https://skillstore.pages.dev/skills/chandlerhardy-chronicle-session-documenter
- Manifest: https://skillstore.pages.dev/api/skills/chandlerhardy-chronicle-session-documenter/manifest

## Capabilities

- Queries Chronicle session summaries through MCP when available.
- Uses Chronicle CLI output as a portable fallback workflow.
- Creates Obsidian session notes with metadata and Markdown sections.
- Adds wikilinks for sessions, repositories, and related commits.
- Supports single-session, daily-session, and topic-based documentation workflows.

## Use Cases

- Create a Daily Development Journal: Turn completed Chronicle sessions into organized Obsidian notes after each workday.
- Prepare Project Handoffs: Summarize accomplishments, decisions, changed files, and blockers for team review.
- Build a Searchable Knowledge Base: Link related sessions, commits, repositories, and topics across a long-running project.

## Prompt Templates

### Document One Session

```
Document Chronicle session 10 to my Obsidian vault.
```

### Document Today

```
Find today's completed Chronicle sessions and create Obsidian notes for them. Ask before overwriting existing notes.
```

### Capture Decisions and Files

```
Create an Obsidian note for session 24. Include accomplishments, key decisions, changed files, blockers, and related commits.
```

### Document Topic History

```
Search Chronicle for sessions about authentication from the last week. Document the three most relevant sessions with wikilinks between related notes.
```

## Limitations

- Requires Chronicle data and either MCP tools or the Chronicle CLI.
- Recent sessions may not have summaries ready immediately.
- CLI output must be parsed from formatted text.
- Sensitive session details should be reviewed before writing to synced vaults.

## Best Practices

- Ask before overwriting any existing Obsidian note.
- Review generated summaries for secrets before syncing notes.
- Prefer MCP data when available because it is structured.

## Anti Patterns

- Do not store session exports in predictable temporary files.
- Do not document active sessions before summaries are ready.
- Do not write private project details to a shared vault without review.

## Security Audit

- Audited at: 2026-07-05T07:10:49.787\+00:00
- Summary: Most static findings are false positives caused by Markdown backticks, code fences, MCP tool names, and scoped Chronicle CLI examples. One confirmed issue remains: the CLI workflow writes session details to a predictable /tmp file, which can expose private development metadata. The skill also has a medium-confidence integrity risk because its main write example uses overwrite mode before the later note-existence warning.

## Stats

- Views: 197
- Downloads: 12
- Favorites: 0
- Popularity score: 0