skills.rest
deerawan
deerawanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gsd-pr-branch

Create a pull request branch with .planning/ changes filtered out.

1|Updated Sep 6, 2015
Search Tags:#git#code review#pull request#branch cleanup#GSD#.planning
One-click install
npx skills add https://github.com/deerawan/dotfiles --skill gsd-pr-branch-deerawan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-pr-branch
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-pr-branch
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-pr-branch-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull requests get cluttered with GSD planning artifacts, making diffs noisy and harder to review.

Core Features & Use Cases

  • Filters out .planning/ changes so reviewers focus on actual code modifications.
  • Creates a clean PR branch from an existing branch by excluding planning-related files from the resulting branch content.
  • Use case: when your current branch includes PLAN/STATE/SUMMARY or other GSD metadata, use this workflow so the PR shows only code deltas.

Quick Start

Ask the AI to create a clean PR branch from your current branch while filtering out .planning/ commits, targeting main by default.

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 from a git pull request diff?▼

To remove .planning files from a pull request diff, you create a review-friendly PR branch that filters out GSD planning artifacts. This workflow excludes .planning/ commit content so reviewers only see actual code modifications.

What is a review-friendly PR branch?▼

A review-friendly PR branch is a git branch that excludes GSD planning artifacts like PLAN, STATE, and SUMMARY metadata. It filters out .planning/ changes so the pull request diff shows only real code deltas.

How do I create a clean PR branch from an existing workflow branch?▼

You create a clean PR branch by applying a filter to your existing workflow branch that removes .planning/ commit content. This targets the main branch by default and produces a branch ready for pull request review.

Does this branch cleanup workflow support branches with mixed GSD metadata and code changes?▼

Yes, this branch cleanup workflow specifically handles branches containing both .planning/ commit content and real code changes. It filters out the GSD planning artifacts while preserving actual code modifications in the resulting branch.

Why does my pull request show noisy diffs with GSD planning artifacts?▼

Your pull request shows noisy diffs because your workflow branch includes GSD planning artifacts alongside real code changes. Creating a clean PR branch filters out the .planning/ metadata so reviewers focus only on code modifications.

Related Skills

Explore More Software Engineering Skills→
tinner-deinnotinner-deinno

gsd-pr-branch

Create a clean PR branch by filtering out .planning/ commit artifacts.

Community
Intermediate
TabooLibTabooLib
388

over-or

Push the current branch to a fork and create a PR to the main repository.

Official
Intermediate
coco-researchcoco-research
264

gsd-pr-branch

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

Community
Intermediate
sduduzogsduduzog

git-advanced-workflows

Automate advanced Git workflows across branches for clean history.

Community
Intermediate