agentleFS
Sign inStart free
SebastianWiercinskiSebastianWiercinski/vibe-session-sync/skills/sync-status/SKILL.md

sync-status

Skill0 starsChanged 7 months agoMITView on GitHub

Compact overview of all registered session-sync sessions in this project, triggered ONLY by the explicit `/sync-status` slash command. Never auto-trigger on natural-language phrases like "sync status", "welche sessions sind aktiv", "show all sessions", or similar — this skill should remain user-initiated. Read-only — shows names, branches, last-active, open questions, scope summaries in a table.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. rohithzr/claudebase★ 26same name
    2. CodesWhat/careerrat★ 4same 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.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If .sync/ or .sync/_active.json missing → say: "Keine Session-Sync in diesem Projekt eingerichtet.

    line 13
  2. Very specific:

    If there are stale sessions (last_active > 7 days), flag them: ⚠️ <name> war zuletzt vor X Tagen aktiv — noch relevant?

    line 52

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

Sync Status

Show a compact overview of all registered sessions and their current state. Read-only — no file updates.

Steps

  1. Check for sync setup:
    • If .sync/ or .sync/_active.json missing → say: "Keine Session-Sync in diesem Projekt eingerichtet. Start mit /sync-init <name>." Exit.
  2. Read _active.json, get list of all registered sessions.
  3. For each session, read .sync/<name>.md and extract:
    • Session name
    • Branch
    • Last active (humanize: "2h ago", "5min ago", "yesterday")
    • Scope (first non-empty line under "## Scope")
    • Count of open questions
    • Count of touched files
    • Any questions tagged at any session (show @targets)
  4. Read _shared.md for mtime — how long since last shared context update.

  5. Output as table:

    📊 Session-Sync Übersicht
Shared context: zuletzt aktualisiert vor X

┌─────────────────────┬───────────────┬─────────────┬──────────┬───────────┐
│ Session             │ Branch        │ Last active │ Files    │ Questions │
├─────────────────────┼───────────────┼─────────────┼──────────┼───────────┤
│ auth-feature        │ feat/auth     │ 10min ago   │ 5        │ 2 → @fe   │
│ checkout-redesign   │ feat/checkout │ 2h ago      │ 12       │ 1 → @be   │
│ admin-dashboard     │ feat/admin    │ yesterday   │ 8        │ 0         │
└─────────────────────┴───────────────┴─────────────┴──────────┴───────────┘

🔔 Offene Fragen zwischen Sessions:
- auth-feature → @checkout-redesign: <first open question>
- checkout-redesign → @auth-feature: <first open question>

Scope per session:
- auth-feature:      JWT-based auth mit Refresh-Token-Rotation
- checkout-redesign: Neues Checkout-Flow mit Stripe Payment Intents
- admin-dashboard:   Admin-UI für User-Management
  6. If there are stale sessions (last_active > 7 days), flag them: ⚠️ <name> war zuletzt vor X Tagen aktiv — noch relevant?

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