skills.rest
dobrinz123
dobrinz123COMMUNITY
Explore all skills by this author →
GitHub

gsd-pr-branch

Rewrite Git branch history to exclude .planning/ commits for clean pull requests.

Updated Apr 9, 2026
Search Tags:#git#workflow#code review#pull request#branch#planning artifacts
One-click install
npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-pr-branch-dobrinz123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-pr-branch
Source: https://github.com/dobrinz123/claude-skills-share/tree/main/skills/gsd-pr-branch
Command: npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-pr-branch-dobrinz123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull request diffs frequently include GSD planning artifacts such as .planning/ commits and files like PLAN.md, SUMMARY.md, and STATE.md, which distract reviewers and obscure the real code changes. This Skill streamlines PR preparation by producing a branch that excludes those planning-only commits so reviewers see only relevant code modifications.

Core Features & Use Cases

  • Filter planning commits: Rewrites branch history or filters the commit set to remove .planning/ commits and related artifacts.
  • Prepare clean PRs: Produces a branch ready for code review without project planning noise.
  • Use Case: When a feature branch accumulated planning files during development, run this workflow before opening a pull request to ensure reviewers only see implementation changes.

Quick Start

Create a clean PR branch from the current branch that excludes .planning/ commits and planning file changes so the diff shows only code changes.

Frequently Asked Questions about gsd-pr-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove planning files like PLAN.md from a git pull request diff?▼

To remove planning files like PLAN.md from a git pull request diff, you can rewrite branch history to exclude .planning/ commits. This filters out planning artifacts so reviewers only see implementation code changes.

Why do my planning artifacts clutter the pull request code review?▼

Planning artifacts clutter code review because feature branches often accumulate .planning/ commits containing files like SUMMARY.md. These artifacts obscure real code modifications and distract reviewers during the pull request process.

What is the best way to create a clean PR branch from a feature branch with planning commits?▼

The best way to create a clean PR branch is to perform a history rewrite or branch filter operation. This preserves your code changes while excluding planning-only commits, resulting in a focused pull request diff.

Can I filter out .planning/ commits from my git history before opening a pull request?▼

Yes, you can filter out .planning/ commits from git history before opening a pull request. The history rewrite operation targets and removes these planning artifacts while maintaining your actual implementation changes.

Do I need a Bash environment to clean up git branches for code review?▼

Yes, you need a Bash-capable environment and access to the repository git history to clean up branches for code review. The history rewrite operation requires these dependencies to filter planning commits effectively.

Related Skills

Explore More Software Engineering Skills→
lgwanailgwanai
4

gsd-pr-branch

Create a pull request branch excluding .planning/ commits from the diff.

Community
Intermediate
yusaduymazyusaduymaz

gsd-pr-branch

Filter planning-only commits from a pull-request branch.

Community
Advanced
mcampbellrmcampbellr

gsd-pr-branch

Remove .planning/ commits from a branch to create a clean pull request branch.

Community
Basic
gesmith0606gesmith0606

gsd-pr-branch

Rewrite Git history excluding commits that modify files in .planning/ to create a pull-ready branch for code review.

Community
Intermediate