Installation and maintenance

Installation and maintenance

What install.sh does, step by step

git clone https://github.com/WhiteMuush/Your-Claude-DevOps.git
cd Your-Claude-DevOps
bash install.sh

In order, it:

1. Creates ~/.claude/skills and ~/.claude/hooks when they do not exist
2. Copies CLAUDE.md into ~/.claude/
3. Copies settings.json into ~/.claude/
4. Copies the 29 skills as a merge, so skills you already have are kept
5. Copies the hooks/ directory
6. Derives the memory project key from $HOME and copies the memory scaffold into ~/.claude/projects/<key>/memory/

The script is idempotent: running it twice does not break anything.

It stops short of one thing. The i-have-adhd plugin is declared in settings.json, with its marketplace, so Claude Code fetches it at the next launch. When that does not happen, install it by hand:

/plugin marketplace add ayghri/i-have-adhd
/plugin install i-have-adhd

Installing through Claude itself

INSTALL.md carries a prompt to paste into Claude Code, which walks the installation and checks it. One detail in it is deliberate: the script writes into ~/.claude/, so the safety gate stops Claude from running it directly. The prompt tells Claude to hand you the command rather than force its way through. That is the right behaviour, not a limitation to work around.

Checking that the installation took

1. ~/.claude/CLAUDE.md exists
2. ls ~/.claude/skills | wc -l answers 29
3. ~/.claude/projects/<key>/memory/MEMORY.md exists
4. The plugin is active, which /plugin will confirm

Customising after install

The configuration is generic on purpose, which means it is also incomplete on purpose. CLAUDE.md describes a profile and a set of preferences that are unlikely to match yours exactly. Rewrite the profile section, and the answer format section, before deciding the configuration does not suit you.

Two things worth reviewing before you trust the defaults:

• The permissions. The deny list blocks gh repo delete, gh repo edit and force pushes. That last pair is uncontroversial; gh repo edit is broader than it looks, since it also covers changing repository visibility. Drop it from the list when that gets in your way.
• defaultMode: auto. Comfortable, and only reasonable because the deny list exists. Tighten it if you work on something where a mistaken command is expensive.

Maintenance

The part that ages is the DevOps skills that pin versions, the nine technology guides. They pin versions and call out deprecations, which is exactly what makes them useful and exactly what makes them go stale. When a provider ships a major version, the skill that names the old one is now actively misleading, because it will be trusted over the training knowledge it was written to override.

There is no automation for this. The practical rhythm is to fix a skill the moment you hit a divergence in real work, rather than auditing them on a schedule.

The method skills age far more slowly. They are adapted from obra/superpowers, so pulling upstream occasionally is the way to refresh them.

Credits

This configuration assembles other people's work, credited in the repository README: the DevOps skills from khalilbenaz/claude-skills-collection, the method skills from obra/superpowers, and the output shaping plugin from ayghri/i-have-adhd.