agentleFS
AbilityaiAbilityai/cornelius/.claude/skills/update-changelog/SKILL.md

update-changelog

Skill109 starsChanged 39 days agoMITView on GitHub

Append a dated entry to the master Brain/CHANGELOG.md summarizing this session's knowledge-graph changes - notes created, connections/links added, and significant edits. Use after a vault working session to record what changed and why it matters.

36 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use clack-cli-patterns, drag-to-reorder and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • openchamberSkill

    clack-cli-patterns

    Use when creating or modifying OpenChamber CLI commands, prompts, terminal output, non-TTY behavior, `--quiet`, or `--json` behavior.

    Also in 3 projects that use this

  • openchamberSkill

    drag-to-reorder

    Use when implementing or modifying OpenChamber sortable or drag-to-reorder behavior, especially `@dnd-kit`, touch/mobile interactions, variable-width items, or wrapping layouts.

    Also in 3 projects that use this

  • mitsuhikoSkill

    oebb-scotty

    Austrian rail travel planner (ÖBB Scotty). Use when planning train journeys in Austria, checking departures/arrivals at stations, or looking for service disruptions. Covers ÖBB trains, S-Bahn, regional trains, and connections to neighboring countries.

    Also in 3 projects that use this

  • mitsuhikoSkill

    pi-share

    Load and parse session transcripts from shittycodingagent.ai/buildwithpi.ai/buildwithpi.com/pi.dev (pi-share) URLs. Fetches gists, decodes embedded session data, and extracts conversation history.

    Also in 3 projects that use this

  • +8 more from openchamber

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 35 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Read Existing Changelog: - Read $VAULT_BASE_PATH/Brain/CHANGELOG.md to see the current state

    line 18
  2. Distinctive:

    Append New Entry: - Add a new dated entry at the TOP of the changelog with:

    line 20
  3. Distinctive:

    Keep each entry to 1-2 sentences maximum

    line 23
  4. Distinctive:

    Use action verbs: CREATED, CONNECTED, UPDATED, LINKED

    line 24
  5. Distinctive:

    Only document changes from THIS session

    line 40
  6. Distinctive:

    Use bidirectional arrows (↔) for mutual connections, directional (→) for one-way

    line 42
  7. Distinctive:

    If no changelog exists, create it with a header explaining its purpose

    line 45
  8. Distinctive:

    After updating, show the user:

    line 49

“Common” is measured: kept by at least 6 in 10 of the 35 edited versions of this file we could read. “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

Update Knowledge Graph Changelog

You are updating the Brain vault changelog to track recent modifications to the knowledge graph.

Your Task

  1. Identify Recent Changes - Review the session history to identify:
    • New notes created
    • New connections/links added between existing notes
    • Significant edits to note content
    • Focus only on changes made during THIS session
  2. Read Existing Changelog - Read $VAULT_BASE_PATH/Brain/CHANGELOG.md to see the current state
  3. Append New Entry - Add a new dated entry at the TOP of the changelog with:
    • Date and session identifier
    • List of changes in format: - [ACTION] Note Title: Brief description (→ Connected to: [[Other Note]])
    • Keep each entry to 1-2 sentences maximum
    • Use action verbs: CREATED, CONNECTED, UPDATED, LINKED

Format Example

## 2025-10-24 - Session [Brief Description]

- CONNECTED [[Psychological Safety]] → [[Flow is impossible without Autonomy]]: Psychological safety creates autonomy prerequisite for flow by removing fear-based constraints.
- CONNECTED [[Radical Ownership]] → [[Flow is impossible without Autonomy]]: True ownership requires autonomy; permission-seeking eliminates both.
- CONNECTED [[Flow is a selfless state]] ↔ [[In Buddhism - Self is an Illusion]]: Flow provides empirical validation of Buddhist insight through performance.
- CONNECTED [[Entrepreneurship is de-risking]] → [[Belief deals with Uncertainty]]: Entrepreneurs hold beliefs about uncertain futures without eliminating uncertainty.
- CONNECTED [[Taking on external obligations]] → [[Radical Ownership]]: Obligations stem from permission-seeking rather than ownership.

Important Guidelines

  • Only document changes from THIS session
  • Be concise - max 2 sentences per change
  • Use bidirectional arrows (↔) for mutual connections, directional (→) for one-way
  • Group related changes together
  • Focus on WHAT was connected and WHY it matters (the insight)
  • If no changelog exists, create it with a header explaining its purpose

Output

After updating, show the user:

  1. Number of changes logged
  2. The new entry you added
  3. Confirmation that CHANGELOG.md was updated

State Dependencies

SourceLocationReadWriteDescription
Master changelogBrain/CHANGELOG.mdXXMain change log to update
Session historyCurrent conversationXChanges made this session

Completion Checklist

  • Session changes identified (notes created, connections made, edits)
  • Existing CHANGELOG.md read
  • New dated entry added at TOP of changelog
  • Action verbs used (CREATED, CONNECTED, UPDATED, LINKED)
  • Entries concise (max 2 sentences each)
  • Arrow notation correct (→ for one-way, ↔ for bidirectional)
  • Number of changes reported to user
  • Confirmation provided that CHANGELOG.md was updated

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.