Personal ~/.claude for Claude Code: settings, global CLAUDE.md, hooks, status line and custom skills, restorable on a new machine with one bootstrap script
FAQ (answers come from our records)
How do I install it?
The repository provides this install command: npx skills. It comes from the repository itself; we cannot guarantee it runs as-is in your client.
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository QingqiShi/claude;first catalogued 2026-10-10;last seen 2026-10-10。There is no official certification or quality rating here — we record sources and dates only.
~/.claude — personal Claude Code config
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Git-backed so a new machine can be restored from scratch. The guiding rule:
> **Commit *references*, not third-party code.** My own skills/config live here as
> source. Third-party plugins & skills are reinstalled from upstream via a
> bootstrap script — never vendored/forked into this repo.
What's tracked vs. reinstalled
| Thing | In git? | Source of truth | Restored by |
|---|---|---|---|
| settings.json, CLAUDE.md, statusline-command.sh, hooks/ | ✅ committed | this repo | git clone |
| **My custom skills** — auto-improve, pr-standards, merge-dependabot, language-sweep, prepare-for-pr | ✅ committed | this repo | git clone |
| **Marketplace plugins** — codex, frontend-design, skill-creator, claude-code-setup | ❌ ignored | settings.json → enabledPlugins + extraKnownMarketplaces | bootstrap.sh → claude plugin install |
| **vercel-cli** skill | ❌ ignored | npx skills add github.com/vercel/vercel --skill vercel-cli | bootstrap.sh |
| **playwright-cli** skill (binary-generated) | ❌ ignored | @playwright/cli npm pkg → playwright-cli install --skills | bootstrap.sh |
The two third-party skill folders (skills/vercel-cli/, skills/playwright-cli/)
are .gitignored — present on disk, absent from git.
New machine setup
Prereqs: git, node/npm, jq, and the claude CLI on PATH.
> Trade-off of the reference model: a bare git clone gives you config + your own
> skills immediately, but the third-party plugins/skills don't exist until
> bootstrap.sh runs.
Keeping third-party skills up to date
Updating is decoupled from git — the third-party skills are ignored, so refreshing
them changes nothing to commit; it just pulls the latest bits onto this machine.
update.sh writes .last-skill-update (timestamp + versions) so you can see how
stale things are.
Optional: run it monthly (macOS launchd)
Runs update.sh at 10:00 on the 1st of each month (login shell → picks up
node/claude PATH). Remove with launchctl unload … then delete the plist.
Adding a new third-party skill/plugin later
- **Plugin:** install as usual; it lands in settings.json → nothing else to do.