skills.rest
D0NMEGA
D0NMEGACOMMUNITY
Explore all skills by this author →
GitHub

gsd-pr-branch

Filter .planning/ commits from the current Git branch for PR-ready changes.

8|Updated Apr 9, 2026
Search Tags:#automation#git#workflow#planning#branch#code-review
One-click install
npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-pr-branch-d0nmega
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-pr-branch
Source: https://github.com/D0NMEGA/donnyclaude/tree/main/packages/skills/gsd-pr-branch
Command: npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-pr-branch-d0nmega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prune planning artifacts from the current Git branch to produce clean, PR-ready code changes.

Core Features & Use Cases

  • Filter out .planning/ commits from the active branch to prevent planning notes from appearing in code review diffs.
  • Preserve code changes while removing non-code metadata, simplifying reviews and CI checks.
  • Use in standard PR workflows where target branch accuracy and history cleanliness matter.

Quick Start

Run the pr-branch workflow to filter planning commits and produce a clean PR 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 remove planning commits from a Git branch before creating a pull request?▼

To clean up Git history before a PR, you need to prune planning artifacts from your active branch. This process filters out .planning/ commits, ensuring reviewers only see source code changes without non-code metadata cluttering the diff.

What is the best way to keep planning notes out of code review diffs?▼

The best way to keep planning notes out of code review diffs is to filter .planning/ commits from your active branch. This pruning process removes non-code metadata from the Git history, ensuring reviewers only see source changes.

How does filtering planning artifacts from a Git branch work?▼

Filtering planning artifacts works by executing a configured workflow that identifies and removes .planning/ commits from the current Git branch. It requires a target-branch argument to accurately filter commits and produce clean code changes.

Do I need a target branch to prune planning commits from my current branch?▼

Yes, you need a target-branch argument to prune planning commits. The workflow requires this target branch to accurately filter commits from the active branch and produce clean, PR-ready code changes.

Can I use branch pruning for standard CI checks and code review workflows?▼

Yes, you can use branch pruning for standard CI checks and code review workflows. Removing .planning/ commits ensures CI pipelines and reviewers only process actual source changes, simplifying the review process.

Why does my pull request include non-code metadata from planning notes?▼

Your pull request includes non-code metadata because planning artifacts were committed to your active Git branch. Running a pr-branch workflow filters these .planning/ commits out, preventing planning notes from appearing in code review diffs.

Related Skills

Explore More Software Engineering Skills→
giovannimnzgiovannimnz

gsd-new-project

Initialize a new project by generating a planning scaffold with PROJECT.md, ROADMAP.md, REQUIREMENTS.md, and STATE.md.

Community
Advanced
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
aporto-techaporto-tech

Ship

Automate code shipping with branch merging, tests, version bumps, commits, and pull requests.

Official
Advanced
paywherebpaywhereb

squash

Squash all branch commits into one via interactive git rebase.

Official
Intermediate