Kevin Veen-BirkenbachandClaude Opus 5
d7e2827511
A bundle was committed on the assumption that it was new. Nobody checked whether another branch already carried the same fix, so the same defect got solved twice and the second solution had to be reconciled by hand at merge time - or worse, silently won. The search that answers this already exists in merge-fix, but merge-fix refuses a dirty tree and commit-next is dirty by definition. So only its search steps are borrowed: fetch every ref, then grep the log by message, by symbol and by path. No cherry-pick, no merge, no touching the staging index. A hit is a stop, not a warning. The staged version and the foreign commit go into dialectic as thesis and antithesis, and the operator gets sha, branch, both diffs, the verdict and one recommended move - keep staged, take theirs, or combine. Committing anyway would decide that question by accident. Nothing found, or the operator picks the staged version, and the old flow continues unchanged from commit-no-verify onwards. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
skills 🧠
The agent skill collection of Kevin Veen-Birkenbach.
Every skill is pinned in skills-lock.json for reproducible installs.
First-party skills live under skills/ and are layered on top of the locked ones at install time.
Compatible with Claude Code, Codex, Gemini CLI, Cursor, Copilot, Windsurf, Cline, and other agents.
Requirements 📦
- Node.js (provides
npx skills). jq(only required formake update).
Installation 🚀
Install the skills globally into your home (~/.agents/skills and ~/.claude/skills):
make install
Copy the skills into a specific project (<repo>/.agents/skills and <repo>/.claude/skills):
make project TARGET=/path/to/repo
Both commands also patch the target's .claude/settings.json: the caveman and ponytail plugins are enabled so their modes auto-activate on session start, and two reminder hooks are registered — autotune points you at /autotune at most once an hour, dream points you at /dream at most once every twelve hours per repository (stamped in that repository's git dir). Existing settings are preserved.
Restart your agent afterwards so it loads the new skills.
Maintenance 🔧
Refresh every skill to its latest version and rewrite skills-lock.json:
make update
Validate skills-lock.json and shellcheck the scripts (also run by CI on every push and after every update):
make test
Related Tools 🧰
This collection is part of a wider toolset for managing IT and infrastructure:
- alias — shell aliases for common commands.
- package-manager —
pkgmgr, a single command to install and manage these repositories. - infinito-nexus — automation platform for self-hosted infrastructure.
License 📜
MIT License, Copyright (c) 2026 Kevin Veen-Birkenbach.
Author 👤
Kevin Veen-Birkenbach kevin@veen.world
Thanks 🙏
Thanks to the #ai:infinito.nexus community, and especially to Paulinhx for the inspiration.
Donation ❤️
If these tools help you, consider supporting their development: