ship-loop-change: choose branch base by checking open PRs - #3
Merged
Conversation
Before creating a branch, check open PRs: branch off main for independent work, but stack on an open PR's head branch when the change depends on it or edits the same files (e.g. append-only LOG.md) — avoids guaranteed merge conflicts. Adds a "Choosing the branch base" section and a matching "Do not" rule. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Adds guidance to the
ship-loop-changeskill: before creating a branch, check open PRs to decide the base — branch offmainfor independent work, but stack on an open PR's head branch when the change depends on it or edits the same files (e.g. append-onlyLOG.md), to avoid guaranteed merge conflicts.gh pr list --json .../gh pr view <n> --json fileschecks and the stack-vs-main rule of thumb.mainwhen an open PR already edits the same files.Stacked on #2 (base
document-skill-system), notmain— because this change editsLOG.md, which #1 and #2 also append to. That's the exact rule this PR documents, applied. GitHub will retarget this tomainonce #1 and #2 merge.🤖 Generated with Claude Code