gsd-pr-branch

Create a pull request branch by filtering out .planning commits.

4|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-pr-branch-electroheadfx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-pr-branch
Source: https://github.com/electroheadfx/efx-mux/tree/main/.codex/skills/gsd-pr-branch
Command: npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-pr-branch-electroheadfx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates a review-ready pull request branch by removing .planning-related commits and keeping code review focused on implementation changes.

Core Features & Use Cases

  • Branch Cleanup: Rebuilds a clean branch history for PRs without planning artifacts.
  • Review Simplification: Prevents PLAN.md, SUMMARY.md, STATE.md, and similar workflow files from cluttering diffs.
  • GSD Workflow Support: Helps teams using Get Shit Done planning files ship code changes cleanly while preserving local planning history.
  • Use Case: You finished a feature with many planning commits and want a branch that only shows the code changes for reviewers.

Quick Start

Use the gsd-pr-branch skill to create a clean pull request branch from the current branch while filtering out .planning commits.

Frequently Asked Questions about gsd-pr-branch

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

FAQPage Schema
How do I create a clean git pull request branch without planning commits?

To create a clean pull request branch, this Skill filters out .planning commits by rewriting branch history. It preserves your code changes while excluding PLAN.md, SUMMARY.md, and STATE.md commits, ensuring reviewers only see implementation changes.

What is the best way to strip planning files from a git branch diff?

Stripping planning files from a git branch diff is done by rebuilding a clean branch history that excludes .planning commits. This removes PLAN.md, SUMMARY.md, and STATE.md artifacts, keeping the code review focused solely on implementation changes.

Can I remove PLAN.md and SUMMARY.md commits from my branch before code review?

Yes, you can remove PLAN.md and SUMMARY.md commits from your branch before code review. The Skill applies branch history rewriting logic to filter out these planning artifacts while preserving all actual code changes for a review-ready diff.

Does git branch cleanup work with GSD workflow development files?

Git branch cleanup works directly with GSD workflow development files by identifying and filtering out .planning-related commits. It helps teams using Get Shit Done planning files ship code changes cleanly while preserving the local planning history on the original branch.

What happens to my local planning history when filtering commits for a PR?

When filtering commits for a pull request, your local planning history remains preserved on the original branch. The Skill creates a separate, review-ready pull request branch by rebuilding the history to exclude .planning commits without destroying the original planning artifacts.

Why do planning artifacts clutter my pull request diffs and how to fix it?

Planning artifacts like PLAN.md, SUMMARY.md, and STATE.md clutter pull request diffs because they are tracked in commit history. To fix it, this Skill rebuilds a clean branch history that excludes these planning commits while keeping your code review focused on implementation changes.