gsd-pr-branch

Filter .planning/ commits to create a clean PR-ready branch.

Updated May 21, 2026
One-click install
npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-pr-branch-jedmamosto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-pr-branch
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-pr-branch
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-pr-branch-jedmamosto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents pull requests from being cluttered with irrelevant commit changes from the .planning directory, so reviewers can focus on actual code differences.

Core Features & Use Cases

  • Clean PR branch creation: Generates a PR-ready branch that omits .planning/ artifacts from the diff.
  • Conflict-free reviewer experience: Produces a branch that keeps review discussions focused on implementation details.
  • Use Case: After following GSD workflows, your working branch contains PLAN.md/SUMMARY.md/STATE.md updates; use this Skill to create a branch where those planning changes do not appear in the PR.

Quick Start

Use the gsd-pr-branch skill to create a clean branch targeting main by filtering out .planning/ commits from your current branch.

Frequently Asked Questions about gsd-pr-branch

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

FAQPage Schema
How do I exclude .planning files from a git pull request diff?

To exclude .planning files from a git pull request diff, use the gsd-pr-branch skill to filter out .planning/ commit changes and generate a clean, PR-ready branch that preserves only meaningful code review differences.

How do I create a clean PR branch that omits planning artifacts?

You can create a clean PR branch by applying the gsd-pr-branch skill to your current working branch, which reads repository state and filters out GSD planning artifacts like PLAN.md, SUMMARY.md, and STATE.md from the final commit history.

Can I remove GSD planning commits from my branch before code review?

Yes, you can remove GSD planning commits from your branch before code review by using the gsd-pr-branch skill to produce a target branch that omits .planning/ directory updates, keeping reviewer discussions focused on implementation details.

What is the best way to hide .planning directory changes in GitHub pull requests?

The best way to hide .planning directory changes in GitHub pull requests is to generate a deterministic branch using the gsd-pr-branch skill, which filters out planning noise so reviewers only see actual code differences.

Does the gsd-pr-branch skill require any special dependencies to filter commits?

No, the gsd-pr-branch skill requires no special dependencies to filter commits; it uses Bash commands to read repository state and produce the target branch specified by the user without needing external components.

Why does my pull request show PLAN.md and SUMMARY.md changes instead of just code?

Your pull request shows PLAN.md and SUMMARY.md changes because GSD workflows update these files in your .planning directory; the gsd-pr-branch skill solves this by creating a clean branch that omits these planning artifacts from the PR diff.