agentleFS
Sign inStart free
claude-worldclaude-world/director-mode-lite/.claude/skills/changelog-observer/SKILL.md

changelog-observer

Skill80 starsChanged 8 months agoMITView on GitHub

Track development session events in a daily markdown changelog, including file changes, test results, and key decisions.

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use .changelog/session-YYYY-MM-DD.md for the current local date.

    line 18
  2. Very specific:

    Create .changelog/ and the session file if they do not exist.

    line 19
  3. Distinctive:

    If the session file is new, initialize it from template.md.

    line 20
  4. Distinctive:

    Keep each description short and specific.

    line 31
  5. Very specific:

    Use none when no files were changed.

    line 33
  6. Distinctive:

    Do not rewrite earlier entries unless they are incorrect.

    line 34
  7. Distinctive:

    Use the markdown structure in template.md for each appended entry.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Changelog Observer

Track session context in .changelog/session-YYYY-MM-DD.md.

Log target

  • Use .changelog/session-YYYY-MM-DD.md for 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 none when 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free