Skip to content

Node-based terminal manager for AI coding agents — tmux-backed terminals and parallel agent sessions as draggable nodes on an infinite pan/zoom canvas. macOS, Linux, and a browser Server Edition.

docs: say how a pull request should read

Howard Youngdahl80ecb1cdf7d5
diff --git a/CLAUDE.md b/CLAUDE.md
index 420fcd56d..e479f3909 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -8,6 +8,11 @@ testing habits). This file is what you reach for when you need to know *why* a r
is, or you are changing a subsystem it describes. A change that other developers must know about
belongs in BOTH (see Conventions).
+**PR text (title, description, comments, review responses) follows the `pr-writing` skill**: what
+changed and why it matters, then how it was checked and what was not, then risks or follow-up when
+there are any. Structure proportional to the change. `CONTRIBUTING.md` § Pull requests is the
+human-facing half of the same rule.
+
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
## What this is
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 0323b48ae..f15e3f0f2 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -416,6 +416,10 @@ production socket on purpose; adding a third is a review conversation, not a che
- Explain **why**, not just what. If a decision has a trade-off, name it and say what you rejected.
- If you measured something, put the numbers in — they save the next person the same afternoon.
- Say what you did **not** verify. That is more useful than a confident summary.
+- **Lead with what changed and why it matters.** A reviewer who reads only your first two
+ sentences should be able to decide whether to keep reading; implementation detail comes after.
+- **Match the length to the change.** A one line fix gets a paragraph, a change that moves a
+ boundary gets as much room as it needs, and neither is improved by headings it does not need.
## Documentation