indifferentketchup
c2b3e0a013
Two portable agent-judgment skills in data/skills/boocode/, externalizing when/how Opus commits and when it isolates work in a worktree, so weaker agents (opencode build agent, BooCoder) can approximate it. committing-changes: segment by concern, stage explicitly (never git add -A), draft scope-prefix messages, present-and-STOP — commit only on explicit command, never push, identity indifferentketchup. using-worktrees: the when-to-isolate heuristic (just-create-when-clear / propose-when-ambiguous / skip), stable-base mechanics, runtime-isolation caveat — deliberately autonomous vs committing's command-gate. Each has an eval.yaml (matching improving-boocode-guidance) with a negative-trigger task. AGENTS.md gets a parser-safe preamble (the registry throws on bare ## headings) pointing at both skills. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
33 lines
2.0 KiB
YAML
33 lines
2.0 KiB
YAML
skill: using-worktrees
|
|
tasks:
|
|
- prompt: "I'm mid-way through a feature but prod is broken — I need to fix it now"
|
|
grader:
|
|
- the response invokes the using-worktrees skill
|
|
- the response recognizes this as a clear case (hotfix interrupting in-progress work) and just creates the worktree rather than asking
|
|
- the response branches the worktree from the stable/default branch, not the in-progress feature branch
|
|
- the response does NOT push
|
|
- prompt: "Let's try a risky refactor of the inference loop and see if it pans out"
|
|
grader:
|
|
- the response invokes the using-worktrees skill
|
|
- the response treats this as a clear case (risky/experimental) and creates a worktree autonomously
|
|
- the response uses a task-derived branch name (no emojis) and a collision-safe path
|
|
- the response notes that project setup must run in the new worktree before it can run
|
|
- prompt: "Should I do this small one-line typo fix in a worktree?"
|
|
grader:
|
|
- the response invokes the using-worktrees skill
|
|
- the response recommends SKIP (small single-stream fix, nothing to isolate) and works in place
|
|
- the response does not create a worktree
|
|
- prompt: "This change is medium-sized and I'm not sure if it'll conflict with what I'm doing"
|
|
grader:
|
|
- the response invokes the using-worktrees skill
|
|
- the response treats this as ambiguous and PROPOSES a worktree in one line, then waits, rather than creating it unilaterally
|
|
- prompt: "Two coder worktrees both run the app on port 9502 — will they be isolated?"
|
|
grader:
|
|
- the response invokes the using-worktrees skill
|
|
- the response explains that worktrees isolate code state but NOT runtime (ports/DBs/services can still collide)
|
|
- the response recommends per-worktree setup to separate the runtime
|
|
- prompt: "What's the difference between git clone and git worktree?"
|
|
grader:
|
|
- the response does NOT invoke the using-worktrees skill
|
|
- the response answers the conceptual question directly
|