skills.rest
tinner-deinno
tinner-deinnoCOMMUNITY
Explore all skills by this author →
GitHub

gsd-pr-branch

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

1|Updated May 24, 2026
Search Tags:#git#code review#pull request#gsd#planning artifacts#branch hygiene#diff cleanup
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-pr-branch-tinner-deinno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-pr-branch
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/gsd/gsd-pr-branch
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-pr-branch-tinner-deinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eliminates clutter in pull requests caused by committing GSD planning artifacts, so reviewers can focus on actual code changes.

Core Features & Use Cases

  • Filters out .planning/ artifacts: Removes commits or file changes related to GSD planning outputs (e.g., PLAN/SUMMARY/STATE) from the PR branch content.
  • Builds a clean PR branch: Produces a branch that aligns with the current branch’s real work while hiding irrelevant planning deltas.
  • Review-focused workflow: Helps teams maintain readable diffs for PRs across engineering cycles that use GSD planning.

Quick Start

Ask the AI to run the gsd-pr-branch skill targeting your main branch to generate a clean PR branch that excludes .planning/ 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 exclude .planning/ files from a pull request diff?▼

To exclude .planning/ files from a pull request diff, you can create a clean PR branch that filters out GSD planning artifacts like PLAN.md and STATE.md, leaving only meaningful code changes for reviewers.

Why does my git pull request show planning artifacts in the diff?▼

Your pull request shows planning artifacts because GSD planning outputs under the .planning/ directory were committed alongside your code. Filtering these planning-only changes from the branch history produces a reviewer-ready diff.

How do I create a clean PR branch without planning noise?▼

You create a clean PR branch by generating a filtered version of your current branch that aligns with your real work while hiding irrelevant planning deltas, ensuring the resulting changeset contains only code changes.

Can I remove GSD planning commits from an existing git branch?▼

Yes, you can remove GSD planning commits by applying a filter to your current branch that excludes .planning/ content, building a clean branch that maintains your actual code changes without the planning noise.

What is the best way to maintain branch hygiene when using GSD planning?▼

The best way to maintain branch hygiene with GSD planning is to build a dedicated PR branch that automatically strips .planning/ artifacts, keeping your engineering workflow diffs readable and focused on code.

When should I filter out planning artifacts before a code review?▼

You should filter out planning artifacts before a code review whenever your GSD workflow commits files like SUMMARY.md or STATE.md, ensuring reviewers only see meaningful code changes rather than planning-only deltas.

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
daddiadaddia
1

create-mr

Create a merge request for the current feature branch targeting the default branch.

Community
Intermediate
sburlsburl
26

repo-assessment

Automate repository health assessments after milestone pull requests using Codex.

Community
Advanced
sunchenddsunchendd
3

git-advanced-workflows

Manage Git history with rebase, cherry-pick, bisect, worktrees, and reflog.

Community
Advanced