gsd-pr-branch

You can remove planning artifacts from a pull request diff by filtering out .planning/ commits. This Skill creates a clean PR branch state so reviewers focus solely on code changes instead of PLAN.md or SUMMARY.md files.

To clean up a git branch before code review, you need to remove unnecessary .planning/ commits. This Skill filters those commits to generate a clean pull request branch, making the diff more readable and efficient.

Planning files like PLAN.md, SUMMARY.md, and STATE.md clutter pull request commits because they are tracked in the .planning/ directory. Removing these planning artifacts ensures code reviewers focus only on the actual code changes.

Yes, you can exclude .planning/ directory commits from your git workflow. This Skill requires a git repository containing a .planning/ directory and removes those specific commits to create a clean pull request state.

Yes, you need a git repository with a .planning/ directory to use this commit filtering approach. The Skill specifically targets and removes commits associated with the .planning/ folder to prepare a clean branch for code review.

The best way to improve code review focus by excluding non-code commits is to filter out .planning/ artifacts. This process removes planning commits from the current branch, ensuring the pull request diff contains only relevant code modifications.