# Use Chronicle Project Memory

AI assistants lose time when they ignore prior Chronicle sessions and roadmap context. This skill guides them to search history, choose MCP or CLI, and reuse project knowledge.

## Install

```bash
npx skillstore add chandlerhardy/chronicle-assistant-guide
```

## Metadata

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

## Capabilities

- Directs assistants to search Chronicle history before Chronicle-related work.
- Shows MCP and CLI options for sessions, commits, roadmap, and milestones.
- Provides workflows for starting tasks, debugging issues, and understanding project history.
- Explains when to prefer MCP tools and when to use CLI fallback.
- Lists common mistakes, quick reference commands, and Chronicle storage locations.

## Use Cases

- Recover Past Implementation Context: Search prior sessions before editing similar code, then reuse successful approaches and avoid repeated mistakes.
- Coordinate Roadmap Work: Review milestones and pending steps before creating new tasks or changing project direction.
- Debug Recurring Issues: Find earlier symptoms, fixes, and failed attempts before proposing a new debugging plan.

## Prompt Templates

### Find Related History

```
Search Chronicle for prior work on [topic]. Summarize the most relevant sessions before suggesting next steps.
```

### Check Planned Work

```
Check Chronicle roadmap and pending next steps for [project]. Tell me what is already planned before we create new work.
```

### Investigate A Bug

```
Use Chronicle to investigate [bug or symptom]. Compare past fixes, failed attempts, and current roadmap items before proposing a fix.
```

### Build A Context Brief

```
Combine Chronicle session search, commit search, and roadmap review for [initiative]. Produce a scoped implementation brief with risks and dependencies.
```

## Limitations

- Requires Chronicle, its MCP server, or its CLI to be installed separately.
- Does not install, configure, or repair Chronicle by itself.
- Search quality depends on the completeness of stored Chronicle sessions and summaries.
- Broad searches can surface sensitive local history if users do not scope queries.

## Best Practices

- Search Chronicle before implementation, debugging, or roadmap changes.
- Use MCP tools when available, and use CLI commands when MCP is not configured.
- Filter by project, date, tool, or topic when broad history is not needed.

## Anti Patterns

- Starting Chronicle-related work without searching prior sessions.
- Reading unrelated session history when a scoped query would be enough.
- Treating generated summaries as final proof without checking relevant details.

## Security Audit

- Audited at: 2026-07-05T07:02:45.717\+00:00
- Summary: The static command findings are false positives from Markdown inline code, code fences, and Chronicle CLI examples. The hidden-file and SQLite findings are documentation of Chronicle storage paths, not direct file access. A semantic privacy issue remains because the guide encourages broad Chronicle searches across all projects without requiring scoping or consent.

## Stats

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