hooks — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited hooks (Hook) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Your Claude brain — everywhere you code.
You spent weeks teaching Claude your codebase. Your architecture decisions. Your team's unwritten rules. Your debugging patterns. Then you opened a new machine and Claude knew nothing.
claude-sync fixes this. One command syncs your entire Claude brain — memory, skills, agents, and rules — across every machine you own and every teammate you work with. It uses Git, so you already have the infrastructure.
claude-sync push # share your brain
claude-sync pull # absorb your team's context
claude-sync merge alice # inherit a teammate's learningscurl -fsSL https://raw.githubusercontent.com/SamTerces/claude-sync/main/install.sh | bashRequires: git, curl, Claude Code Recommended: jq (for settings merging — brew install jq)
| Layer | Path |
|---|---|
| Memory | ~/.claude/memory/ |
| Skills | ~/.claude/skills/ |
| Agents | ~/.claude/agents/ |
| Rules | ~/.claude/CLAUDE.md |
| Settings | ~/.claude/settings.json (safe keys only) |
API keys, tokens, .env files, and logs never leave your machine. See skills/claude-sync/references/security.md for the full scrub contract.
Every developer gets a personal branch in a shared Git repo (brain/<username>). Team content lives on main. You push your learnings to your branch and pull shared context from main. Merging is always opt-in and interactive — nothing overwrites silently.
you (work laptop) origin/brain/you origin/main
│ │ │
push ──────────────────▶ │ │
│ merge ──────────────────▶ │
│ │ merge ──┤◀── alice
pull ◀──────────────────────────────────────── │| Command | What it does |
|---|---|
claude-sync init <url> | First-time setup with a Git remote |
claude-sync push | Push local brain to origin/brain/<you> |
claude-sync pull | Pull origin/main into local brain |
claude-sync diff | Show what differs from remote |
claude-sync merge <name> | Absorb a teammate's learnings |
claude-sync status | Brain inventory + sync state |
claude-sync watch | Auto-push after memory/skill writes |
claude-sync unwatch | Disable auto-push |
Or inside Claude Code: /sync push, /sync pull, /sync diff, etc.
Full details: skills/claude-sync/references/merge-strategy.md
Local always wins by default. Conflicts are shown before any file is touched. --force is never used — --force-with-lease only.
Full details: skills/claude-sync/references/conflict-resolution.md
See EXAMPLES.md for quick reference, or skills/claude-sync/EXAMPLES.md for full walkthroughs covering: solo multi-machine, team onboarding, contractor setup, auto-sync, and conflict handling.
ageclaude-sync invite <email> — send a teammate a one-command onboarding linkPRs welcome. One concern per PR. See CLAUDE.md for guidelines on modifying skill triggers, sync behaviour, and the security scrubbing contract.
MIT
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.