Sync the live ~/.claude global config (settings.json, CLAUDE.md, statusline.ts, own skills, skills.sh lock file) into this git backup repo, then commit. Allowlist-based so credentials, history, and project transcripts are never copied. Use when the user says "sync my claude config", "back up .claude", "update the .claude repo", or runs "/sync-claude".
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Backs up the user's live global Claude Code config (~/.claude) into this repo.
This is a project skill of the backup repo, it is not installed globally.
Only these paths are ever read (the allowlist lives in sync.ts):
~/.claude/settings.json, CLAUDE.md, statusline.ts~/.claude/skills/* that are NOT listed in the skills.sh lock file. These are
the user's own skills and are mirrored into skills/<name>/.~/.agents/.skill-lock.json, the manifest the skills.sh CLI keeps for skills
it installed into ~/.agents/skills and symlinked into ~/.claude/skills.
Copied to .agents/.skill-lock.json. Those skills are never vendored here;
install-skills.ts reinstalls them from the lock on a new machine.Everything else in ~/.claude (.credentials.json, history.jsonl, projects/,
sessions/, todos/, tasks/, ...) is never read. That allowlist is the primary
defense against leaking secrets. A value-shaped secret scan on the copied content
is a second safety net: if a key or token ever appears inside an allowlisted file,
that file (or that whole skill) is skipped.
From the repo root, show what would change (copies nothing):
bun .claude/skills/sync-claude/sync.ts
orphan lines are skill folders in the repo that are not live own skills.
A skill "managed by skills.sh" got vendored by mistake: delete it from
skills/. A skill "not in ~/.claude/skills" was removed live: delete it, or
copy it back to ~/.claude/skills/ if the removal was an accident.
Apply the copy:
bun .claude/skills/sync-claude/sync.ts --apply
If it exits non-zero, a possible secret was detected. Stop, show the user the flagged line, and do not commit.
Review and commit on main (this repo commits directly to main, no PR):
git status
git diff
git add -A settings.json CLAUDE.md statusline.ts skills .agents
git commit -m "chore: sync live .claude config"
Do not push unless the user asks.
bun .claude/skills/sync-claude/install-skills.ts --list # print the commands
bun .claude/skills/sync-claude/install-skills.ts # run them
One bunx skills add <source> -g -y -a claude-code -s <names> per source repo.
statusline.ts is the source. The live status line runs the compiled
statusline binary, which is large and not tracked.FILES in
sync.ts (and make sure it never contains secrets).まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Monitor a pull request through review and CI until it's green: verify every bot claim against the code, fix what's real, push back on what's wrong, rerun flaky checks. Use when the user asks to babysit, monitor, watch, or shepherd a PR, says "get this PR green" or "handle the review comments". Accepts an optional PR number/URL; defaults to the current branch's open PR.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a single unified changelog from git history that works for everyone in the company (managers and non-tech colleagues as well as developers). Outputs Slack mrkdwn so it can be pasted straight into Slack. Defaults to Slovak (English only on explicit request) and to comparing the release branch (main) against develop to show unreleased changes; also supports date ranges like "today", "yesterday", "last week", or an explicit git range. User-invoked only via /changelog.
日本語の概要は準備中です。原文の説明を表示しています。
Create atomic git commits with terse, exact Conventional Commits messages. Cuts noise, preserves intent. Subject ≤50 chars. Body only when "why" isn't obvious. Use when the user says "commit", "commit this", "/commit", or asks to stage and commit changes.
日本語の概要は準備中です。原文の説明を表示しています。
Create atomic git commits with terse Conventional Commits messages, then push to remote. Subject ≤50 chars, body only when "why" isn't obvious. Never force pushes. Use when the user says "commit and push", "commit & push", "/commit-push", or asks to stage, commit, and push in one flow.
日本語の概要は準備中です。原文の説明を表示しています。
Create branch, atomic commits, push, and open a pull request with terse, exact messages. Conventional branch + commit format. PR title ≤70 chars, body says "why", not "what". Use when the user says "create pr", "create pullrequest", "create pull request", "make pr", "open pr", "open pullrequest", "open pull request", "submit pr", "raise pr", "/create-pr", or asks to ship/send changes as a pull request (PR/pullrequest/pull-request, any spelling).
日本語の概要は準備中です。原文の説明を表示しています。