Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Tighter daily format, no metrics sections, more personal voice
What This Skill Does
DevChronicle generates prose narratives of developer work by reading git history, OpenClaw session transcripts, and memory files. Output formats include daily chronicles, weekly rollups, standups, and portfolio write-ups. The focus is on decisions and rejected approaches, not just completed tasks.
Synthesizes git history, session transcripts, and memory files into narrative prose rather than requiring manual note-taking or manual assembly of commit logs.
When to use it
- Writing standup notes from yesterday's commits
- Reviewing a week's direction changes and pivots
- Generating a portfolio case study from a finished project
- Capturing what was killed or rejected during a day of work
- Summarizing a sprint for a team update
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: What did I do this week?
- 1Read config.json for project directories, memory dir, and sessions dir
- 2Run gather.sh with a 7-day range to collect raw data
- 3Read git commits across all configured repos for the period
- 4Scan memory files and relevant session transcripts for decisions and context
- 5Generate a weekly narrative chronicle covering themes, decisions made, and rejected approaches
A multi-section narrative chronicle covering the week's work arcs, what shipped, what was cut, and where things are heading