agentleFS
Sign inStart free
AbilityaiAbilityai/cornelius/.claude/skills/changelog-protocol/SKILL.md

changelog-protocol

Skill109 starsChanged 38 days agoMITView on GitHub

Protocol for creating dated changelog files after significant agent sessions. Use when completing vault operations, discovery sessions, insight extraction, or any work requiring documentation.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    MANDATORY: Before starting any session, call:

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Protocol

All sub-agents MUST create separate dated changelog files after each significant session.

File Location & Naming

  • Directory: Brain/05-Meta/Changelogs/
  • Naming Format: CHANGELOG - [Session Type] YYYY-MM-DD.md
  • Examples:
    • CHANGELOG - Auto-Discovery Sessions 2025-10-25.md
    • CHANGELOG - Connection Discovery Session 2025-10-24.md
    • CHANGELOG - Vault Management Session 2025-10-26.md
    • CHANGELOG - Insight Extraction Session 2025-10-27.md

Timestamp Requirements

MANDATORY: Before starting any session, call:

date '+%Y-%m-%d %H:%M:%S %Z'

Include this timestamp at the top of the changelog file. Use the date from this command in the filename.

Changelog Content Structure

Each changelog file must include:

  1. Session header with date, time, and session type
  2. Session overview with key statistics
  3. Major discoveries/connections/changes documented in detail
  4. Emergent patterns or meta-insights
  5. Synthesis opportunities identified
  6. Session statistics (notes analyzed, connections found, etc.)
  7. Recommended next actions

When to Create Changelogs

AgentTrigger
Auto-Discovery AgentAfter every discovery session (mandatory)
Connection Finder AgentAfter every connection mapping session (mandatory)
Vault Manager AgentAfter significant CRUD operations affecting 3+ notes
Insight Extractor AgentAfter extracting insights from significant content

Dual Logging System

  • Dated files: Individual session logs in /05-Meta/Changelogs/ folder (primary, detailed)
  • Master CHANGELOG.md: Summary entries in /Brain/CHANGELOG.md (secondary, brief)

The dated changelog files are the primary record - comprehensive and detailed. The master CHANGELOG.md serves as a quick reference index with brief entries pointing to the detailed session files.

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