agentleFS
Sign inStart free
tylergibbs1tylergibbs1/breadcrumb/SKILL.md

breadcrumb

Skill1 starsChanged 10 months agoMITView on GitHub

Leave notes on files for other agents to see in future sessions. Use after making non-obvious changes, fixing tricky bugs, or when code looks wrong but is intentional.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. couimet/my-claude-skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

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:

    Leave notes on files that persist across agent sessions.

    line 17
  2. Distinctive:

    After making changes that future agents might misunderstand:

    line 21
  3. Distinctive:

    Use judgment: the warning might still apply, or might be outdated

    line 62
  4. Distinctive:

    After reviewing stale notes, update hashes with:

    line 69
  5. Distinctive:

    All commands output JSON. Key fields:

    line 76

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

Breadcrumb

Leave notes on files that persist across agent sessions.

When to use

After making changes that future agents might misunderstand:

  • Non-obvious code that looks like it could be simplified
  • Bug fixes for edge cases
  • Intentional workarounds
  • Security-critical patterns
  • Performance tuning

Core workflow

1. Before editing, check for warnings:

breadcrumb check ./src/api/users.ts
  • Exit 0 = safe to proceed (clear/info)
  • Exit 1 = warning exists, read the suggestion field

2. After non-obvious changes, leave a note:

breadcrumb add ./src/api/users.ts "Retry logic tuned for rate limits"

Command reference

CommandPurpose
breadcrumb check <path>Check path for notes (-r for recursive)
breadcrumb add <path> <message>Leave a note (-s severity, --ttl expiration)
breadcrumb edit <path-or-id>Edit a note (-m message, -a append, -s severity)
breadcrumb verify [path]Check if notes are stale (--update to refresh hashes)
breadcrumb search <query>Find notes by content (-r for regex)
breadcrumb coverage [path]Show breadcrumb coverage stats
breadcrumb lsList all notes (-s filter by severity)
breadcrumb statusQuick overview (counts)
breadcrumb rm <path>Remove a note (-i by ID)
breadcrumb pruneRemove expired notes

Staleness detection

Notes track file content hashes. When you see [STALE] prefix:

  • The file has changed since the note was written
  • The note may no longer be accurate
  • Use judgment: the warning might still apply, or might be outdated
📝 BREADCRUMB: [STALE] Don't simplify this regex
                ↑ Code changed - verify note still applies

After reviewing stale notes, update hashes with:

breadcrumb verify --update

Output format

All commands output JSON. Key fields:

  • status: "clear", "info", or "warn"
  • suggestion: Actionable guidance when warnings exist
  • breadcrumbs: Array of matching breadcrumb objects
  • staleness: "verified", "stale", or "unknown" (per breadcrumb)

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