Klaussy update
Refresh this repository's klaussy-generated boilerplate to match the latest klaussy version, for every agent klaussy previously scaffolded.
Steps
Upgrade klaussy first. Run
pipx upgrade klaussy-agents(orpip install --user --upgrade klaussy-agentsif klaussy wasn't installed via pipx) — the PyPI distribution isklaussy-agents, notklaussy. Verify the new version withklaussy --version. Note the version for the report at the end.Read the existing version marker.
cat .claude/skills/.klaussy-versioncaptures 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 bumpedklaussy-repo-conventionsand want to re-run the path-scoped CLAUDE.md emission).Detect the base branch the same way
klaussy-initdoes (git branch --list dev develop main master | head -1).Run
klaussy init --force. The--forceflag overrides the version-skip check and rewrites all generated files with the new templates:klaussy init --force --base-branch <detected> $ARGUMENTSDiff the result. Run
git diffover the generated files for every scaffolded agent — Claude (CLAUDE.md,.claude/) plus any ofGEMINI.md/.gemini/,AGENTS.md(Codex/Antigravity),.cursor/,.github/copilot-instructions.md/.github/skills/,.clinerules/,.opencode/,.kimi-code/,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.
If
klaussy initprinted "This clone uses --local", the generated files are in.git/info/excludeandgit diffwon't show them. Summarize from klaussy's own output instead, and skip the reminder to commit: in a local clone there's nothing to commit.Report. Tell the user the old marker version → new version and what materially changed in the generated content. Remind them to commit, unless
klaussy initprinted "This clone uses --local".
When NOT to use
- The user wants klaussy's files gone rather than refreshed — that's the
klaussy-uninstallskill. Re-runninginit --forcerewrites them, it never removes them. - The repo isn't klaussified yet — use the
klaussy-initskill instead (runningklaussy init --forceon 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, orklaussy settingsdirectly withoutinit --force. - The user pinned an older klaussy version intentionally and doesn't want to upgrade — skip step 1 and re-run
klaussy init --forceagainst the existing version, but flag that this is unusual.