agentleFS
Sign inStart free
AbilityaiAbilityai/cornelius/.claude/skills/propagate-change/SKILL.md

propagate-change

Skill109 starsChanged 38 days agoMITView on GitHub

Propagate staleness from a changed note through the Brain Dependency Graph - shows which downstream notes need review

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    When a note is substantially edited, this skill computes which downstream notes may be stale and need review.

    line 12
  2. Distinctive:

    If the user wants details on any affected note:

    line 45
  3. Distinctive:

    After substantially editing a framework or key insight note

    line 52
  4. Distinctive:

    When the user says they've updated their thinking on a topic

    line 53
  5. Distinctive:

    After ingesting new source material that contradicts existing notes

    line 54

≈ “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

Propagate Framework/Note Change

When a note is substantially edited, this skill computes which downstream notes may be stale and need review. Uses the Brain Dependency Graph's staleness propagation engine with edge-type decay, distance decay, and hub dampening.

State Dependencies

SourceLocationReadWriteDescription
Enrichmentsresources/brain-graph/data/graph_enrichments.json✓✓Updated staleness scores
LBS Graphresources/local-brain-search/data/brain_graph.pkl✓NetworkX graph

Process

Step 1: Run propagation

cd $PROJECT_ROOT/resources/brain-graph
../local-brain-search/venv/bin/python cli.py propagate "<NOTE_NAME>"

Optional: specify change magnitude (0.0-1.0) for partial changes:

../local-brain-search/venv/bin/python cli.py propagate "<NOTE_NAME>" --magnitude 0.5

Step 2: Present affected notes

Show the user which notes are flagged for review, sorted by staleness score.

For each affected note, explain:

  • Why it's flagged (which upstream change, through what edge type)
  • Suggested action: review, update, or mark as OK

Step 3: Offer to inspect specific notes

If the user wants details on any affected note:

../local-brain-search/venv/bin/python cli.py inspect "<NOTE_NAME>"

When to Use

  • After substantially editing a framework or key insight note
  • When the user says they've updated their thinking on a topic
  • After ingesting new source material that contradicts existing notes

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