gsd-pr-branch

To exclude planning files from a git pull request diff, you need to create a clean PR branch that filters out planning-only commits. This separates workspace artifacts like PLAN.md from actual code changes before review.

Preparing a review-ready git branch involves filtering out planning commit history from your current feature branch. This process preserves your code changes while removing planning artifacts, producing a clean diff against the main branch.

Yes, you can remove planning commits from a feature branch without losing code changes. The branch cleanup process preserves all implementation work while specifically targeting and filtering out planning-only commits from the commit history.

Yes, this branch cleanup workflow applies directly to standard Git-based code review processes. It generates a review-friendly branch against a target branch such as main, ensuring reviewers only see relevant code modifications.

Planning artifacts typically filtered out during PR branch cleanup include planning files such as PLAN.md, SUMMARY.md, and STATE.md. These workspace artifacts are removed from the reviewer diff to maintain focus on code changes.