How do I install the Klaussy Update skill?

Run npx skillmds@latest add steph-dove/klaussy-update in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Klaussy Update safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Klaussy Update?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Klaussy Update free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Klaussy Update?

steph-dove (@steph-dove) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Klaussy Update by steph-dove — Agent Skill

Name: Klaussy Update
Author: steph-dove

Klaussy Update

Use when the user wants to refresh klaussy-generated boilerplate (per-agent conventions, skills, settings, hooks) across every scaffolded agent after upgrading klaussy itself. Re-runs the scaffold against the latest templates so this repo picks up new skills, prompt revisions, and convention rules.

steph-dove Updated Sep 17, 2026

File contents

Klaussy update

Refresh this repository's klaussy-generated boilerplate to match the latest klaussy version, for every agent klaussy previously scaffolded (Claude Code, Gemini CLI, Cursor, Codex, GitHub Copilot, Google Antigravity, Cline, Aider).

Steps

Upgrade klaussy first. Run pipx upgrade klaussy (or pip install --user --upgrade klaussy if klaussy wasn't installed via pipx). Verify the new version with klaussy --version. Note the version for the report at the end.
Read the existing version marker. cat .claude/skills/.klaussy-version captures the version that last generated the skills. If the new klaussy version is the same as the marker, klaussy will skip — surface that to the user and confirm they want to proceed anyway (rare; usually only useful if you've also bumped klaussy-repo-conventions and want to re-run the path-scoped CLAUDE.md emission).
Detect the base branch the same way klaussy-init does (git branch --list dev develop main master | head -1).
Run klaussy init --force. The --force flag overrides the version-skip check and rewrites all generated files with the new templates:
```
klaussy init --force --base-branch <detected> $ARGUMENTS
```
Diff the result. Run git diff over the generated files for every scaffolded agent — Claude (CLAUDE.md, .claude/) plus any of GEMINI.md/.gemini/, AGENTS.md (Codex/Antigravity), .cursor/, .github/copilot-instructions.md/.github/skills/, .clinerules/, CONVENTIONS.md (Aider) that exist — and summarize the substantive changes for the user:
- New skills added or removed
- Prompt body changes in <repo>-plan / <repo>-review / etc.
- New / changed rule files (e.g. under .claude/rules/)
- Settings or hook changes This is the user's chance to review before committing the refresh.
Report. Tell the user the old marker version → new version, what materially changed in the generated content, and remind them to commit.

When NOT to use

The repo isn't klaussified yet — use the klaussy-init skill instead (running klaussy init --force on a clean repo works but the skill auto-detect is cleaner).
The user only wants to update one specific surface (just skills, just hooks, just settings) — they can run klaussy skills, klaussy hooks, or klaussy settings directly without init --force.
The user pinned an older klaussy version intentionally and doesn't want to upgrade — skip step 1 and re-run klaussy init --force against the existing version, but flag that this is unusual.

---name: klaussy-updatedescription: Use when the user wants to refresh klaussy-generated boilerplate (per-agent conventions, skills, settings, hooks) across every scaffolded agent after upgrading klaussy itself. Re-runs the scaffold against the latest templates so this repo picks up new skills, prompt revisions, and convention rules.---# Klaussy updateRefresh this repository's klaussy-generated boilerplate to match the latest klaussy version, for every agent klaussy previously scaffolded (Claude Code, Gemini CLI, Cursor, Codex, GitHub Copilot, Google Antigravity, Cline, Aider).## Steps1. **Upgrade klaussy first.** Run `pipx upgrade klaussy` (or `pip install --user --upgrade klaussy` if klaussy wasn't installed via pipx). Verify the new version with `klaussy --version`. Note the version for the report at the end.2. **Read the existing version marker.** `cat .claude/skills/.klaussy-version` captures the version that last generated the skills. If the new klaussy version is the same as the marker, klaussy will skip — surface that to the user and confirm they want to proceed anyway (rare; usually only useful if you've also bumped `klaussy-repo-conventions` and want to re-run the path-scoped CLAUDE.md emission).3. **Detect the base branch** the same way `klaussy-init` does (`git branch --list dev develop main master | head -1`).4. **Run `klaussy init --force`.** The `--force` flag overrides the version-skip check and rewrites all generated files with the new templates: ``` klaussy init --force --base-branch <detected> $ARGUMENTS ```5. **Diff the result.** Run `git diff` over the generated files for every scaffolded agent — Claude (`CLAUDE.md`, `.claude/`) plus any of `GEMINI.md`/`.gemini/`, `AGENTS.md` (Codex/Antigravity), `.cursor/`, `.github/copilot-instructions.md`/`.github/skills/`, `.clinerules/`, `CONVENTIONS.md` (Aider) that exist — and summarize the substantive changes for the user: - New skills added or removed - Prompt body changes in `<repo>-plan` / `<repo>-review` / etc. - New / changed rule files (e.g. under `.claude/rules/`) - Settings or hook changes This is the user's chance to review before committing the refresh.6. **Report.** Tell the user the old marker version → new version, what materially changed in the generated content, and remind them to commit.## When NOT to use- The repo isn't klaussified yet — use the `klaussy-init` skill instead (running `klaussy init --force` on a clean repo works but the skill auto-detect is cleaner).- The user only wants to update one specific surface (just skills, just hooks, just settings) — they can run `klaussy skills`, `klaussy hooks`, or `klaussy settings` directly without `init --force`.- The user pinned an older klaussy version intentionally and doesn't want to upgrade — skip step 1 and re-run `klaussy init --force` against the existing version, but flag that this is unusual.

Frequently asked questions