skills.rest
ArtRiv
ArtRivCOMMUNITY
Explore all skills by this author →
GitHub

gsd-pr-branch

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

Updated Feb 11, 2026
Search Tags:#git#code review#pull request#ci workflow#branch automation#diff hygiene
One-click install
npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-pr-branch-artriv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-pr-branch
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-pr-branch
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-pr-branch-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull requests often get cluttered with non-code planning artifacts from the current branch, making review harder and diffs harder to understand.

Core Features & Use Cases

  • Clean PR branch creation: Produces a new branch suitable for PR review by excluding .planning/-related commits.
  • Reviewer-friendly diffs: Ensures reviewers primarily see real code changes rather than GSD planning metadata.
  • Workflow-driven execution: Runs the referenced PR-branch workflow end-to-end to apply the filtering consistently.

Quick Start

Run the pr-branch workflow end-to-end from the skill workflow at @.github/get-shit-done/workflows/pr-branch.md while targeting the branch you want to open for review (defaulting to main if none is provided).

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 artifacts from a pull request branch?▼

To exclude planning artifacts from a pull request branch, generate a clean PR branch that filters out .planning/ commits from your current working branch, leaving only code-relevant changes for review.

Why does my pull request diff show non-code files and metadata?▼

Your pull request diff shows non-code files because GSD planning artifacts and metadata are committed to your current branch. Filtering these .planning/ commits into a separate review branch produces a cleaner, code-only diff.

How do I create a clean PR branch for code review from a noisy working branch?▼

You create a clean PR branch by running the pr-branch workflow end-to-end, which applies consistent filtering to remove planning commits. You can optionally specify a target branch, defaulting to main if none is provided.

Does this PR branch filtering work with the main branch as a target?▼

Yes, the PR branch filtering works with main as the default target branch. You can also provide an optional target branch argument to open the review against a different base branch.

What is the best way to remove GSD planning commits before opening a pull request?▼

The best way to remove GSD planning commits is to use a workflow-driven execution that consistently filters .planning/ artifacts. This produces reviewer-friendly diffs by ensuring reviewers primarily see real code changes.

Related Skills

Explore More Software Engineering Skills→
gralwebgralweb

workflow

Automate Git workflows from branch creation to PR notifications.

Community
Advanced
FerroxLabsFerroxLabs
21

ferrox-pr-branch

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

Community
Intermediate
nanorepublicananorepublica
61

Global Tech Stack

Validate code against centralized global tech stack standards.

Community
Basic
Fandry96Fandry96
27

git-advanced-workflows

Rewrite Git commit histories using interactive rebases, cherry-picking, and reflog recovery.

Community
Advanced