docs: add PR-overlap guideline to CLAUDE.md#325
Merged
Conversation
… 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.
Collaborator
Author
|
Hi @addyosmani @federicobartoli, could you take a look when you have a moment? |
Owner
|
Merging. Sensible anti-overlap guideline that codifies the coordinate-before-you-open-a-PR habit we've needed. Thanks @nucliweb. |
addyosmani
approved these changes
Jun 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a
## Pull Requestssection and a Boundaries bullet toCLAUDE.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. It also nudges toward small, focused PRs over large refactors of widely shared files.Why
There was no guidance to check for in-flight work before opening a PR, and it bit us in practice: #324 was opened without noticing #323, which was already open against the same file (
scripts/validate-skills.js) and overlapping on the same rule (the description "when to use" trigger). The result is a guaranteed merge conflict and duplicated effort that a quick scan of open PRs would have prevented.The wording is intentionally generic about remote names (
origin/upstreamare mentioned only as the common convention) so it applies regardless of how a contributor's remotes are set up.Scope
Docs only. No code or validator behavior changes.