claudefiles plugin
claudefiles deploys a personal Claude Code setup onto a new machine: skills, commands, hooks and settings from a single manifest.
- 120 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The install runs a network script via `curl | bash`, edits `~/.claude/settings.json` and adds hooks on session events.
- Optional features call third-party npm installers.
Install
- Works in
Manual install
curl -fsSL https://raw.githubusercontent.com/koolamusic/claudefiles/main/bootstrap.sh | bashThe README quick install clones the repo to `~/.claudefiles`, then `/setup` is run.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The install runs a network script via `curl | bash`, edits `~/.claude/settings.json` and adds hooks on session events.
- Optional features call third-party npm installers.
This is third-party code. Review the repository files before installing.
What it does
claudefiles, like dotfiles for Claude Code, keeps skills, commands, hooks, sounds and `settings.json` in a repository and deploys them to `~/.claude/`. The `/setup` command reads the `claudefiles.yaml` manifest, detects macOS or Linux, copies files and merges settings after making a backup. The set includes skills for Go, Rust, NestJS, React, documents and PDF, the `/gitcommit` and `/gitconfig` commands, and the jira, warden, studio, ux and pstack plugins. Experimental features such as trust-monitor and tower are enabled only if you agree during setup.
Who it is for. Developers who run Claude Code on a laptop, VMs and servers and want an identical setup everywhere from one command.
Good fit when
- A fresh VM should get your usual Claude Code skills, commands and sounds.
- You want a ready example of a manifest and hook layout for your own set.
- A sprint workflow with research, plan, execute and review skills is the base you need.
- One settings set is kept in sync between macOS and Linux.
Not a fit when
- You use other agents: the repository targets only Claude Code.
- `~/.claude/settings.json` and hooks must not be changed on this machine.
- Policy forbids running a script from the internet without reading it.
Example request
Read `claudefiles.yaml`, list which files and hooks `/setup` will place in `~/.claude/`, and only then deploy.Limitations
The repository is personal and built around the author's taste: StarCraft sounds, Obsidian and a Node.js, Rust, Go stack. The quick install runs `bootstrap.sh` through `curl | bash`, and `/setup` edits `~/.claude/settings.json` and installs hooks, so read the manifest and script first. The gsd and raydr options call third-party npm installers. Only Claude Code on macOS and Linux is supported. The last commit is from October 2026. The repository relies on specific external projects and may need manual fixes if they change.
How to disable. Remove the added skills, commands and hooks from `~/.claude/`, restore `settings.json` from the backup and delete the `~/.claudefiles` clone. Uninstall plugins through `/plugin`.
FAQ
How do I install without curl and bash?
Use the manual route: `git clone` into `~/.claudefiles`, then run `claude "/setup"` from that folder.
What does /setup do?
It detects the platform, copies skills, commands, hooks and sounds to `~/.claude/`, merges `settings.json` with a backup and asks about experimental features.
What is trust-monitor?
An optional session trust ladder: hooks gate tools by level and a bar shows in the statusline. It is enabled only if you opt in.
Which skills are included?
Among them agent-browser, docx, pdf, pptx, xlsx, golang, rust and nestjs best practices, react-best-practices, handoff, grill, retro and others.
What do the hooks do?
They watch context usage, remind about retrospectives and start one after a finished phase. Trust monitoring is a separate opt-in.
Discussion
No questions or reviews yet.
Related
PluginsOne-command Claude Code environment installer: a wizard sets up agents, rules, commands, skills and hooks in three profiles
A handbook and starter set for Claude Code: guides, CLAUDE.md templates, starter kits, hooks and the commit-helper plugin.
A set of slash commands, skills and subagents for Claude Code: review, tests, security, releases, docs and GitHub to Linear sync
Claude Code Blueprint: 12 agents, 19 skills, 16 hooks and 6 CLAUDE.md rules, copy what you need or install a preset
An installer giving Claude Code rules for phases, decision logs, debugging and tests in Go, Rust, Python and six more languages.
A Claude Code environment installer: CLAUDE.md, rules, skills, agents, hooks and two-layer project memory in one script
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| claudefiles (this card) | no | 120 | |
| claude-config | no | 916 | a Claude Code settings set; claudefiles deploys them from a manifest with a backup and hooks |
| codex-claude-code-config | no | 214 | shared config for Codex and Claude Code; claudefiles targets Claude Code only and adds plugins and sounds |
README in short
The idea is that Claude reads the manifest and configures itself, so there are no complex bash installers. Most skills come from open repositories with the source credited.