breadcrumb
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.
What this skill does
# 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:**
```bash
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:**
```bash
breadcrumb add ./src/api/users.ts "Retry logic tuned for rate limits"
```
## Command reference
| Command | Purpose |
|---------|---------|
| `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 ls` | List all notes (`-s` filter by severity) |
| `breadcrumb status` | Quick overview (counts) |
| `breadcrumb rm <path>` | Remove a note (`-i` by ID) |
| `breadcrumb prune` | Remove 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:
```bash
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)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.