agentleFS
Sign inStart free
rohithzrrohithzr/claudebase/skills/sync-status/SKILL.md

sync-status

Skill26 starsChanged 8 months agoMITView on GitHub

Use when the user wants to check what config has changed, see sync status, or compare local vs remote config. Trigger with /sync-status.

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. CodesWhat/careerrat★ 4same name
    2. SebastianWiercinski/vibe-session-sync★ 0same 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

6 rules. About 0 are common, 5 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the documented script and check its result.

    line 26
  2. Distinctive:

    Run the diff script:

    line 28
  3. Very specific:

    If the user doesn't specify a profile, omit the --profile flag (uses active profile).

    line 34
  4. Distinctive:

    Read the README for installation, shared layers, and supported configuration paths.

    line 68
  5. Distinctive:

    Read the privacy policy for backup storage and credential handling.

    line 69
  6. Distinctive:

    Read the changelog for changes affecting installed versions.

    line 70

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

Config Sync Status

Overview

Compare the current local Claude Code configuration with its saved GitHub profile. Use this skill before deciding whether to push local edits or restore remote changes. It reports differences without applying the saved configuration or publishing local changes.

Prerequisites

Claudebase must be initialized, with Bash, jq, Git, and authenticated GitHub CLI access to the backup repository. The requested profile must exist. Run from the intended project directory so the comparison uses the correct local configuration.

Instructions

  1. Parse the requested arguments and select the appropriate options below.
  2. Run the documented script and check its result.

Run the diff script:

bash ${CLAUDE_PLUGIN_ROOT}/scripts/diff-config.sh --profile PROFILE_NAME

If the user doesn't specify a profile, omit the --profile flag (uses active profile).

Interpreting output

The script shows each tracked file/directory with a status:

  • + local only (green) — Exists locally but hasn't been pushed yet
  • + remote only (cyan) — Exists in the repo but hasn't been pulled yet
  • ~ modified (yellow) — Exists in both but differs

Recommendations

Based on the output, suggest the appropriate action:

  • Local-only files → suggest /sync-push
  • Remote-only files → suggest /sync-pull
  • Modified files → suggest checking what changed, then push or pull

Output

Report each local-only, remote-only, and modified file or directory using the meanings below. Summarize the recommended next action based on the comparison. Check the script result before claiming configurations match; a failed comparison does not establish that no changes exist.

Error Handling

Troubleshoot incomplete setup with /sync-setup. For a missing profile, suggest listing profiles with /sync-profiles list. If authentication or repository refresh fails, report the failure and restore access before rerunning the comparison. Keep recommendations separate from executing a push or pull.

Examples

/sync-status
/sync-status --profile work

Resources

  • Read the README for installation, shared layers, and supported configuration paths.
  • Read the privacy policy for backup storage and credential handling.
  • Read the changelog for changes affecting installed versions.

User Arguments

Interpret the following input as arguments for the documented operation:

$ARGUMENTS

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