agentleFS
Sign inStart free
revealui-studiorevealui-studio/revskills/skills/revealui-sync-lts/SKILL.md

revealui-sync-lts

Skill2 starsChanged 40 days agoMITView on GitHub

DEPRECATED 2026-07-02 — the per-repo LTS sync model (bundle/mirror declared in .claude/lts-mode) is retired. Disaster recovery is the weekly whole-distro WSL snapshot (Windows scheduled task RevealUI-WSL-Weekly-Backup, shipped as revkit scripts/weekly-wsl-backup.ps1 with staleness alerting). Retained for reference; will be removed in a future revskills major.

  • Commits and pushes

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Read <repo>/.claude/lts-mode.

    line 59
  2. Very specific:

    If bundle: create dated bundle, prune old, verify via cd /mnt/e/professional/<RepoName> && git bundle verify <file>.

    line 60
  3. Very specific:

    If mirror: verify bare clone exists, verify lts remote, push all refs + tags.

    line 61
  4. Very specific:

    Do not run git -C <path> — use cd <repo> && cmd per bash.md.

    line 66
  5. Very specific:

    Do not auto-create an lts remote or bare clone — that's a one-time setup the user should authorize.

    line 67
  6. Distinctive:

    Do not delete older bundles below the retention floor without confirming.

    line 68

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

DEPRECATED 2026-07-02

The per-repo LTS model this skill drives (.claude/lts-mode = bundle | mirror, per-repo copies under the LTS drive) was retired when disaster recovery moved to weekly whole-distro WSL snapshots (wsl --export via the Windows scheduled task RevealUI-WSL-Weekly-Backup; source + staleness alerting live in revkit scripts/weekly-wsl-backup.ps1 + scripts/check-backup-staleness.ps1). GitHub remains the source of truth for repo content. Do not re-adopt per-repo bundles/mirrors; leftover .claude/lts-mode files are stale residue.

The original skill body follows for historical reference.

Sync RevealFleet repos to the LTS drive. LTS mode is declared per-repo at .claude/lts-mode (values: bundle or mirror). If absent, refuse to sync and prompt user to declare.

Load helpers:

. "$REVEALFLEET_ROOT/revskills/scripts/lib/session-state.sh"

Modes

bundle — dated git bundle snapshots, no live clone

  • Destination: /mnt/e/professional/<RepoName>/
  • Action: cd <repo> && git bundle create /mnt/e/professional/<RepoName>/<repo>-$(date +%Y%m%d-%H%M).bundle --all
  • Retain last 10 bundles, prune older.

mirror — live bare clone at LTS, pushed on sync

  • Destination: /mnt/e/professional/<RepoName>.git (bare clone)
  • Precondition: remote lts configured in repo; /mnt/e/professional/<RepoName>.git exists as bare repo.
  • Action: cd <repo> && git push lts --all && git push lts --tags

Steps

  1. Discover LTS mount: mount | grep /mnt/e — fail if not mounted.
  2. For each RevealFleet repo (iterate $REVEALFLEET_ROOT/*/ excluding dotfiles):
    • Skip if not a git repo.
    • Read <repo>/.claude/lts-mode. If missing, print unconfigured: <repo> and continue.
    • If bundle: create dated bundle, prune old, verify via cd /mnt/e/professional/<RepoName> && git bundle verify <file>.
    • If mirror: verify bare clone exists, verify lts remote, push all refs + tags.
  3. Report: per-repo status line (<repo>: mode=bundle | bundles=10 | latest=<file> or <repo>: mode=mirror | ahead=0 | behind=0).
  4. Uncommitted changes: for any repo with unstaged/staged changes, list them under a "Not yet backed up (working tree)" section — bundles/mirrors only capture committed state.

Do not

  • Do not run git -C <path> — use cd <repo> && cmd per bash.md.
  • Do not auto-create an lts remote or bare clone — that's a one-time setup the user should authorize.
  • Do not delete older bundles below the retention floor without confirming.

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.

Reviews can't be read right now.

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