skills.rest
tomascortereal
tomascorterealCOMMUNITY
Explore all skills by this author →
GitHub

gsd-pr-branch

Filter .planning/ commits from Git branches to create clean pull requests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates clutter in pull request diffs by removing GSD planning artifacts (PLAN.md, SUMMARY.md, STATE.md) that distract reviewers from actual code changes.

Core Features & Use Cases

  • Isolated Code Review: Generates a branch containing only code commits, excluding all .planning/ directory artifacts
  • Automated Workflow: Executes the standardized pr-branch workflow from the GSD system
  • Use Case: Perfect for developers using GSD who need to submit clean PRs without exposing planning documents to reviewers

Quick Start

Run the gsd-pr-branch skill to create a clean PR branch 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, you can filter out `.planning/` commits to generate a clean PR branch. This isolates code changes from GSD planning artifacts like PLAN.md and SUMMARY.md.

Why does my pull request show planning documents in the code review?▼

Your pull request shows planning documents because GSD artifacts are committed alongside code changes. Running a pr-branch workflow filters these `.planning/` directory files out, ensuring reviewers only see actual code modifications.

How do I create a clean PR branch from my current Git workflow?▼

You can create a clean PR branch by executing the standardized pr-branch workflow from the GSD system. This process automatically generates a new branch containing only your isolated code commits.

Can I separate GSD planning artifacts from code commits for code review?▼

Yes, you can separate GSD planning artifacts from code commits for code review. This Skill specifically filters `.planning/` directory commits to ensure planning documents remain separate from the review process.

Do I need the GSD system to generate filtered pull request branches?▼

Yes, you need the GSD system to generate filtered pull request branches. This Skill requires execution of the pr-branch workflow from the GSD-managed development workflow to properly isolate code changes.

Related Skills

Explore More Software Engineering Skills→
MINT-IAMINT-IA

gsd-forensics

Diagnose failed GSD workflow executions and generate evidence-backed forensic reports.

Official
Advanced
dmzoneilldmzoneill
2

review-pr

Automate Git merge request reviews across GitLab with commit, pipeline, and Jira checks.

Community
Advanced
tinner-deinnotinner-deinno

gsd-pr-branch

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

Community
Intermediate
ArogyaReddyArogyaReddy

git-advanced-workflows

Teach interactive rebase, cherry-pick, bisect, worktrees, and reflog workflows.

Community
Advanced