Skip to content
TakoAPI
Back to skills

dev-chronicle

by sssamuelll

Notes & PKM
453Downloads reported by clawskills.sh
0Views
0 likesSign in to like this skill
—Not yet rated
Your rating

Brief

Generate narrative chronicles of developer work from git history, session transcripts, and memory files.

Description

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

INPUT

User asks: What did I do this week?

AGENT
  1. 1

    Read config.json for project directories, memory dir, and sessions dir

  2. 2

    Run gather.sh with a 7-day range to collect raw data

  3. 3

    Read git commits across all configured repos for the period

  4. 4

    Scan memory files and relevant session transcripts for decisions and context

  5. 5

    Generate a weekly narrative chronicle covering themes, decisions made, and rejected approaches

OUTPUT

A multi-section narrative chronicle covering the week's work arcs, what shipped, what was cut, and where things are heading

Installation

clawhub install sssamuelll/dev-chronicle

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links