Kevin Veen-Birkenbach
ebe7886654
kvb-git-branch-gc becomes kvb-git-branch-cleanup and kvb-git-orphans-find becomes kvb-git-worktree-orphans, which drops its own orphans.py for pkgmgr's output. New wrappers: kvb-git-gc, kvb-git-worktree-cleanup and kvb-git-worktree-up. kvb-cleanup, kvb-dream, AGENTS.md and README.md point at the new names. Merges only after the pkgmgr release that ships these commands. 🎯 Fix: 90 % 💥 Break: 3 % 💸 Cost: new ⏱️ Time: new 🛡️ Security: 100 % 🏆 Score: 87 🚦 Gate: cost new, time new: cleared by the operator's commit word for the Skills wrappers (2026-11-07) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 18dade9a48a84761bf0c3a9b35584367ae0cb0e4)
1.9 KiB
1.9 KiB
Agent Instructions
Platform-agnostic development
Everything in this repository MUST work on every agent runtime, not only on the one developing it: Claude Code, Codex, Gemini CLI, Hermes, OpenClaw and any other that reads skills. The same holds for operating systems and distributions.
- Logic in scripts: behaviour lives in
python3orbashscripts that any runtime can call. Hooks, plugins and settings of one runtime are thin adapters over those scripts, never the only path to a feature. - Skills stay portable: a
SKILL.mdthat uses a runtime-specific tool (AskUserQuestion,SendMessage, a slash command) says what the step needs, so another runtime can use its own equivalent. - Installs reach every runtime: install into the cross-runtime locations
(
~/.agents/skills) or through an installer that configures every detected agent; runtime-specific locations are mirrors. Of a tool that ships both, take the agent-agnostic integration over one runtime's plugin, and never both: the same server would run twice. - No single package manager: an install never depends on one OS or distribution's package manager; prefer upstream or statically linked release builds.
- One instruction file: rules live here and nowhere else; no
CLAUDE.md,CLAUDE.local.mdorGEMINI.md. Claude Code reads this file natively from v2.1.277; Gemini CLI once itscontext.fileNamesetting listsAGENTS.md.
Scope against package-manager
Deterministic logic an operator could run without an agent (branches,
worktrees, cleanups, releases) lives in
package-manager as
a pkgmgr command with its tests, never as a script in a skill. A skill
wrapping it holds only the agent discipline: claims, picks, handover.
Code questions
Ask the codebase-memory-mcp graph first (search_graph, trace_path,
get_architecture); grep only after it.