Changelog Observer
SkillFiles & storageTrack development session events in a daily markdown changelog, including file changes, test results, and key decisions.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Changelog Observer skill
What this skill tells your AI
The instructions your AI receives, as published by claude-world/director-mode-lite in .claude/skills/changelog-observer/SKILL.md and read by ahel’s review.
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.
Signals
- GitHub stars
- 82
- Forks
- 11
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
changelog-observer- Source
- github.com/claude-world/director-mode-lite