Changelog observer
Skill claude-world/director-mode-lite/.claude/skills/changelog-observer
Track development session events in a daily markdown changelog, including file changes, test results, and key decisions.From its SKILL.md
npx -y skills add claude-world/director-mode-lite --skill changelog-observerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.1 KB, 195 tokens by cl100k_base, as published. Nobody here has run it
Changelog Observer
Track session context in .changelog/session-YYYY-MM-DD.md.
Log target
- Use
.changelog/session-YYYY-MM-DD.mdfor the current local date. - Create
.changelog/and the session file if they do not exist. - If the session file is new, initialize it from template.md.
- Append new entries in chronological order.
What to log
file-change: after creating, editing, or deleting project files.test-result: after running tests, checks, or validation commands.decision: after making an implementation or architecture decision worth preserving.
Entry rules
- Keep each description short and specific.
- List only directly affected files.
- Use
nonewhen no files were changed. - Do not rewrite earlier entries unless they are incorrect.
Template
Use the markdown structure in template.md for each appended entry.
What ships with it: 1 file
188 B alongside SKILL.md
- template.md188 B
Gives 0 of the 12 instructions most readme changelog skills give in 195 tokens
Counted across 446 of the 460 authors here whose files we hold, read 2026-09-06
- Follow Keep a Changelog formatin 24 of 446
- Collect commits since the last git tagin 15 of 446, across 13 files
- Omit empty sectionsin 14 of 446
- Put breaking changes first with migration stepsin 14 of 446
- Include migration guidance for breaking changesin 11 of 446, across 10 files
- Categorize commits by conventional commit prefixin 11 of 446
- Mark breaking changes prominentlyin 10 of 446
- Prepend the new entry to CHANGELOG.mdin 9 of 446
- Highlight breaking changes with migration notesin 8 of 446, across 7 files
- Classify changes into Keep a Changelog categoriesin 8 of 446, across 7 files
- Group related commits into single entriesin 8 of 446
- Write the changelog from commitsin 8 of 446
Said here and by no other author read
- Append session events to the daily changelog file
- Initialize new session files from the template
- Append new entries in chronological order
- Keep each description short and specific
- List only directly affected files
- Use none when no files were changed
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.