菜单
Session continuity for coding work. Default to /chronicle to capture, /chronicle catchup to resume, and /chronicle pending to review open threads. Use curate, recap, wrapup, summarize, publish, insights, search, and ui only when the user explicitly needs them.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/fairchild/dotclaude --skill chronicle命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Speak text aloud (TTS) and transcribe speech (STT). Supports local (macOS say, mlx-whisper) and cloud (ElevenLabs) providers. Use when user asks to speak, read aloud, listen, transcribe, or use vocal.
Work with Claude Code configuration at global (~/.claude) or project (.claude/) level. Use when editing settings.json (permissions, hooks, statusline, model), managing MCP servers, creating agents/commands/skills, writing CLAUDE.md, setting up rules files, or configuring a new project. Determines context automatically and provides guidance on global vs project placement to avoid duplication.
Analyze local AI coding-assistant activity across Claude Code, Codex, Cursor, and Pi. Use when the user asks about coding usage, tool or skill statistics, activity patterns, repositories, sessions, token costs, conversation history, or wants to query their AI coding logs. Triggers include "usage", "how much have I used", "most used tools", "skill popularity", "coding stats", "activity patterns", and "session history".
正在显示 SKILL.md
基于 SOC 职业分类
| name | chronicle |
| description | Session continuity for coding work. Default to /chronicle to capture, /chronicle catchup to resume, and /chronicle pending to review open threads. Use curate, recap, wrapup, summarize, publish, insights, search, and ui only when the user explicitly needs them. |
| license | Apache-2.0 |
Captures and curates session memory so coding context survives across restarts.
Related: For persistent teammate behavior see team-memory. For session title lifecycle see session-titles.
Prefer these three workflows unless the user explicitly asks for something else:
/chronicle # Save current session state
/chronicle catchup # Restore context for the current project
/chronicle pending # Show open threads across sessions
Use them like this:
/chronicle when the user wants to save, checkpoint, or quickly wrap a session./chronicle catchup when the user is returning to a repo and wants to know where they left off./chronicle pending when the user wants a project-spanning open-loops list.| Need | Command | How to respond |
|---|---|---|
| Quick capture | /chronicle or /chronicle <note> | Summarize current state, write/update today's block, keep output concise. |
| Return briefing | /chronicle catchup | Load recent blocks for the current project and surface active context first. |
| Open loops | /chronicle pending | List pending items across blocks; group by project when helpful. |
| Help | /chronicle help or /chronicle ? | Start with the three primary workflows; expand into advanced commands only if the user asks. |
| Curated memory | /chronicle curate | Invoke the curator agent for a richer block instead of doing a thin capture. |
| Session closeout | /chronicle wrapup | Run deliberate closeout: curate, inspect unresolved work, and update backlog only when warranted. |
| Narrative recap | /chronicle recap | Generate a multi-session narrative, cross-checking git and blocks. |
| Search/read | /chronicle search, /chronicle blocks, /chronicle stale, /chronicle resolve | Use the matching script and report exact matches or resolution state. |
| Publish/UI | /chronicle publish, ui, dev | Use the docs/scripts only when the user asks for exported or browser views. |
| Summaries | /chronicle summarize | Generate time-bucketed AI summaries for human consumption. |
For full command behavior, examples, and edge cases, read references/command-reference.md.
For /chronicle catchup, run the catchup script or manually read recent project blocks, then answer in this order:
For /chronicle pending, show active items first. Do not bury stale or resolved material in a long historical dump.
Use chronicle-curator when the user wants a meaningful checkpoint, retrospective, or session wrap. Curated blocks should include goal, accomplishments, decisions, challenges, and next steps.
/chronicle wrapup is a closeout workflow, not just a summary. Check whether pending work belongs in backlog, whether the session is safe to archive, and whether local processes or branches need cleanup.
Run scripts from the Chronicle script directory unless the command reference says otherwise:
bun ~/.claude/skills/chronicle/scripts/catchup.ts
bun ~/.claude/skills/chronicle/scripts/recap.ts <project> --days=14
bun ~/.claude/skills/chronicle/scripts/stale.ts
bun ~/.claude/skills/chronicle/scripts/resolve.ts "<pending item>"
bun ~/.claude/skills/chronicle/scripts/publish.ts --period weekly
bun ~/.claude/skills/chronicle/scripts/dashboard.ts
Use repo-local paths (skills/chronicle/scripts/...) when developing this repo.
For Chronicle implementation work:
docs/development.md for local development workflow../skills/chronicle/tests/run_tests.sh for the browser-backed flow tests.bun test commands in skills/chronicle/scripts/ for script changes.Load additional context only when needed:
references/command-reference.md — full command details, examples, schemas, UI/publish/summarize behavior.docs/chronicle-design.md — system design.docs/dashboard-service.md — dashboard service details.docs/development.md — development workflow.