Skip to content
Skills Library
Programming · Writing

chronicle

/chronicle

Maintain and update the persistent project chronicle (docs/chronicle.md). Trigger when: - The human requests a history summary or chronicle update. - Starting work on a new codebase and needing context on its evolution. - Prompt contains keywords: /chronicle, chronicle, project history, git log summary, history summary.

Author
nrdxp ↗
Repository
predicate ↗
Licence
MIT
Last repository change
31.08.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 31.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/update_chronicle.py

What it does and when to use it

Maintain and update the persistent project chronicle (docs/chronicle.md). Trigger when: - The human requests a history summary or chronicle update. - Starting work on a new codebase and needing context on its evolution. - Prompt contains keywords: /chronicle, chronicle, project history, git log summary, history summary.

Original author description

Maintain and update the persistent project chronicle (docs/chronicle.md). Trigger when: - The human requests a history summary or chronicle update. - Starting work on a new codebase and needing context on its evolution. - Prompt contains keywords: /chronicle, chronicle, project history, git log summary, history summary.

How it works

  1. Purpose
  2. Execution Protocol
  3. Output Format Guidelines
Original SKILL.md headings · 59 lines, 443 words
SKILL.md preview
---
name: chronicle
description: |
  Maintain and update the persistent project chronicle (docs/chronicle.md).
  Trigger when:
  - The human requests a history summary or chronicle update.
  - Starting work on a new codebase and needing context on its evolution.
  - Prompt contains keywords: /chronicle, chronicle, project history, git log summary, history summary.
---

# Chronicle Workflow

A structured approach to maintaining a high-level, conceptual project chronicle (`docs/chronicle.md`). This chronicle serves as a persistent decision record, mapping the evolution of the codebase's architecture, workflows, and conventions to optimize agent context and human understanding.

---

## Purpose

Standard git logs are either too detailed or too fragmented to provide deep architectural context. The **Chronicle Workflow** maintains an incremental, high-level chronicle file in the repository. Because it uses a commit cutoff marker in its frontmatter, it can be updated cheaply and incrementally over time, serving as a durable project history journal.

---

## Execution Protocol

To update or initialize the chronicle, follow these steps:

### 1. Prepare Pending Logs
Run the helper script in prepare mode:
```bash
python3 skills/chronicle/scripts/update_chronicle.py --prepare
```

If the chronicle is already up to date, the script will output:
`Chronicle is already up to date with HEAD.` and you may exit.

Otherwise, it will output a batch of up to 50 commits (from oldest to newest) along with changed files. Note the `TARGET_END_SHA` printed at the end of the output — you pass it back to the write step so the recorded range is bound to exactly the commits you summarized (immune to HEAD moving in between).

### 2. Group and Summarize
Using your LLM reasoning, analyze the batch output. Group the commits into conceptual themes rather than listing them raw. Focus on **why** changes were made, what design decisions were reached, and major milestones.

Organize the summary into the following categories where relevant:
- **Architectural Shift / Design Decisions**: Major structural changes, folder reorganizations, and key trade-offs.
- **Workflow & Rulesets**: Updates to workflows, rulesets, and agent configurations.
- **Features & Implementation**: Core user-facing features and implementations.
- **Infrastructure & Quality**: CI, tooling, linting, and test configurations.
- **Documentation**: Significant documentation changes (beyond minor typos).

### 3. Commit the Update
Run the helper script in write mode, passing the `TARGET_END_SHA` from Step 1 and your structured Markdown summary:
```bash
python3 skills/chronicle/scripts/update_chronicle.py --write --end-sha <TARGET_END_SHA> --summary "<Markdown formatted summary>"
```

### 4. Repeat
If the write command output indicates remaining pending commits (e.g., `Remaining pending commits: N`), repeat from Step 1 until the prepare command reports that it is fully up to date.

---

## Output Format Guidelines

The chronicle summaries should be written in clean, concise Markdown. Avoid listing individual commit SHAs in the summary text (the headers already track the ranges). Example format:

```markdown
- **Architectural Shift**: Distilled global ruleset to align with axiom/persona conventions.
- **Workflow & Rulesets**: Formalized planning workflows by adding `SKETCH` and `PLAN` protocols.
- **Quality & Infrastructure**: Ignore cache files and standardize tooling in the root configuration.
```
Files in this package (2)
  • SKILL.md 3 KB
  • scripts/update_chronicle.py 8 KB

Versions

RepositoryScoreLicence
This page · nrdxp/predicate100MIT
microsoft/vscode100MIT
alexander-tyagunov/magician100MIT
carlheath/ogmios100MIT

Database snapshot: 13.11.2026 · package version c624444de1d3 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 86chronicle-graph
    Curate the user's Chronicle knowledge graph yourself, so nodes carry recognizable titles and hold what the user actually did. Use when the user asks to organize, clean up, or make sense of their Chronicle graph or a recording, especially when Chronicle has no model of its own set up.
  • 100chronicle-context
    Ground work in what the user has actually been doing on this computer. Use before computer-use actions, when the user refers to something they saw, searched, opened, or worked on ("that page", "the ticket from earlier", "what I was researching"), when continuing a task they…
  • 100contextsutra-decision-chronicle
    List engineering decisions and ADRs with their declared status, source line and whether anything still needs a human decision. Use when asked "why did we choose X", "which ADRs are current" or "is this decision approved".
  • 100git-review
    Goal-directed review of git history for change coherence. Trigger when: - Analyzing project history, reviewing diffs, or checking commit messages for alignment. - Prompt contains: /git-review, git history, commit log, change coherence.
  • 100fact-check
    Fact-checking and quality review of texts. [WHAT] Verifies claims, checks sources, identifies style issues. Can be used standalone or piped after /chronicle. [WHEN] Use when: fact-check, verify, check, quality check. [EXPERTISE] Fact-checking, source verification, style review.
  • 80vc:docs
    Use when you need to analyze a codebase and initialize, update, or summarize project documentation.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.