From 90e315a7269aa702523a515d86bc67944fa59a87 Mon Sep 17 00:00:00 2001 From: Joan Leon Date: Thu, 25 Jun 2026 09:54:58 +0200 Subject: [PATCH] docs: require checking upstream PRs/issues for overlap before opening a PR Add a Pull Requests section and a Boundaries bullet to CLAUDE.md: before opening a PR, search the upstream repo's open PRs and issues for overlapping work and coordinate instead of opening a conflicting PR. Wording is generic about remote names so it applies regardless of fork setup. --- CLAUDE.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 7332a48..2faf8bc 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -36,8 +36,16 @@ docs/ → Setup guides for different tools - `npm test` — Not applicable (this is a documentation project) - Validate: Check that all SKILL.md files have valid YAML frontmatter with name and description +## Pull Requests + +PRs target the upstream repository's default branch. In a typical fork setup the upstream remote is `upstream` and your fork is `origin`, but the exact remote names are not what matters here. + +- Before opening a PR, search the upstream repository's open PRs and issues for work that touches the same files or rules. If any overlaps, coordinate (build on it, align your rules with it, or rebase after it merges) instead of opening a conflicting PR. +- Prefer small, focused PRs over large refactors of widely shared files (for example, files under `scripts/`), which are more likely to collide with in-flight work. + ## Boundaries - Always: Follow the skill-anatomy.md format for new skills +- Always: Check the upstream repo's open PRs and issues for overlap before opening a new PR - Never: Add skills that are vague advice instead of actionable processes - Never: Duplicate content between skills — reference other skills instead