Skip to content

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows

skills(running-tend): hold approval on contributor PRs whose code outweighs the fix's reach (#4296)

Worktrunk Boteb67f2980be7
diff --git a/.claude/skills/running-tend/references/review-pr.md b/.claude/skills/running-tend/references/review-pr.md
index 477a5aa46..cc22275ce 100644
--- a/.claude/skills/running-tend/references/review-pr.md
+++ b/.claude/skills/running-tend/references/review-pr.md
@@ -72,6 +72,25 @@ learns that they wouldn't already assume, and how many readers need it. When the
answer is nothing, ask for its removal in the review rather than approving past
it.
+**Proportionality and the canonical approach:**
+
+A correct diff is not yet an approval. Approve only when the change leaves the
+codebase better, weighing the code it adds against how many users the fix
+reaches:
+
+- A rare corner case fixed with a lot of new code — a new helper or parser, a
+ parameter threaded through many call sites, a new error-handling branch — is
+ not a clear win. Name the cost, and the smaller alternative if you see one,
+ such as reusing an existing parser or reading an already-cached value.
+- Special-casing one error, variant, or input where the underlying problem is
+ general suggests the fix sits at the wrong layer. Ask whether it should be
+ handled generally.
+- Before accepting new machinery, find how the codebase already solves the same
+ problem, and ask the author to reuse that rather than add a second copy.
+
+When one of these holds, submit `COMMENT` naming it rather than `APPROVE`, even
+after every correctness finding is closed.
+
**Duplication search patterns (Rust-specific):**
```bash