agentleFS
paslavskyipaslavskyi/llm-wiki/.claude/skills/kb-recap/SKILL.md

kb-recap

Skill1 starsChanged 33 days agoMITView on GitHub

Use on request to summarize what changed in the knowledge base over a time range or area ("what did we do today", "what changed about users") — a read-only narrative from git history. Saves nothing.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Run node tools/session-delta.mjs with those flags → facts (added / updated / deleted notes under knowledge/, optionally area-filtered).

    line 16
  2. Distinctive:

    Write the narrative: what was added, changed, deprecated, and any new open questions in that range.

    line 20
  3. Distinctive:

    If the range is empty: "No changes in that period."

    line 24
  4. Distinctive:

    Read-only. Never write notes, never commit, never create a journal file.

    line 27

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

kb-recap — optional, read-only history recap

Goal: answer a user's question about recent changes with a narrative built from git facts. Persistence is automatic and separate — recap never saves anything.

Steps

  1. Parse the requested range from the user:
    • time: "today" / "this week" → --since "<date>"
    • area: "about users" / a domain → --area <folder>
    • "since last commit" → --ref <ref>
  2. Run node tools/session-delta.mjs with those flags → facts (added / updated / deleted notes under knowledge/, optionally area-filtered).
  3. For richer narrative, you MAY read a few of the changed notes' summaries via kb-recall (index-first) — do not read the whole tree.
  4. Write the narrative: what was added, changed, deprecated, and any new open questions in that range.
    • debug: include ids.
    • autonomous: plain language, no ids/mechanics.
  5. If the range is empty: "No changes in that period."

Rules

  • Read-only. Never write notes, never commit, never create a journal file.
  • Index-first if you open anything; never read the whole knowledge tree.

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.