agentleFS
AbilityaiAbilityai/cornelius/.claude/skills/coherence-sweep/SKILL.md

coherence-sweep

Skill109 starsChanged 38 days agoMITView on GitHub

Run a full coherence sweep across the Brain Dependency Graph - computes staleness, lifecycle transitions, structural health, and generates a report

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run a full coherence analysis of the knowledge base using the Brain Dependency Graph engine.

    line 12
  2. Distinctive:

    If not bootstrapped, run bootstrap first:

    line 36
  3. Distinctive:

    Default (7-day lookback, lifecycle included, no tensions):

    line 43
  4. Distinctive:

    Read the generated report and present key findings to the user:

    line 62

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

Brain Coherence Sweep

Run a full coherence analysis of the knowledge base using the Brain Dependency Graph engine. Identifies stale notes, lifecycle transitions, structural issues, and optionally productive tensions.

State Dependencies

SourceLocationReadWriteDescription
LBS Graphresources/local-brain-search/data/brain_graph.pkl✓NetworkX graph
Enrichmentsresources/brain-graph/data/graph_enrichments.json✓✓Node/edge enrichments
Reportsresources/brain-graph/reports/✓Generated reports

Prerequisites

  • Brain Dependency Graph must be bootstrapped (run_brain_graph.sh bootstrap)
  • Local Brain Search index must exist

Process

Step 1: Check bootstrap status

cd $PROJECT_ROOT/resources/brain-graph
../local-brain-search/venv/bin/python cli.py status

If not bootstrapped, run bootstrap first:

../local-brain-search/venv/bin/python cli.py bootstrap

Step 2: Run coherence sweep

Default (7-day lookback, lifecycle included, no tensions):

../local-brain-search/venv/bin/python cli.py coherence

With options:

# Include tension detection (slower)
../local-brain-search/venv/bin/python cli.py coherence --tensions

# Custom lookback period
../local-brain-search/venv/bin/python cli.py coherence --days 14

# JSON output
../local-brain-search/venv/bin/python cli.py coherence --json

Step 3: Present results

Read the generated report and present key findings to the user:

  1. Staleness alerts - Notes that need review due to upstream changes
  2. Lifecycle transitions - Notes crossing phase boundaries (reflective -> crystallizing -> generative)
  3. Structural health - Orphans, overloaded hubs, missing MOCs
  4. Tensions (if enabled) - Productive contradictions for synthesis

Report is saved to: resources/brain-graph/reports/coherence-report-YYYY-MM-DD.md

Output Format

Present a concise summary with:

  • Count of stale notes with top 5 most affected
  • Notable lifecycle transitions (especially new generative notes)
  • Structural issues requiring attention
  • Path to full report

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.