skills.rest
Poom5741
Poom5741COMMUNITY
Explore all skills by this author →
GitHub

gsd-pr-branch

Filter Git feature branches by removing planning artifact commits for PR-ready code-only diffs.

Updated Mar 15, 2026
Search Tags:#git#workflow#cleanup#branch#pr#code-review#planning-artifacts
One-click install
npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-pr-branch-poom5741
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-pr-branch
Source: https://github.com/Poom5741/eggo-world-pb/tree/main/.qwen/skills/gsd-pr-branch
Command: npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-pr-branch-poom5741

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remove planning artifacts from a feature branch so the PR shows only code changes, speeding up reviews and reducing noise.

Core Features & Use Cases

  • Cleanly filter out .planning/ and other planning-related commits from the target branch.
  • Produce a code-focused PR ready for reviewers.
  • Use within standard git workflows to keep history meaningful and review-friendly.

Quick Start

Create a clean PR-ready branch from your current branch by filtering out planning artifacts.

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 artifacts from a git branch before creating a PR?▼

Removing planning artifacts from a git branch involves filtering out commits with .planning/ directories so the PR contains only code changes. This ensures reviewers see clean diffs without planning notes, speeding up the review process.

Why does my pull request diff show planning notes and non-code commits?▼

Your pull request diff shows planning notes because the feature branch includes planning artifact commits. Filtering the branch to remove these .planning/ commits produces a code-focused PR ready for reviewers without the noise.

How do I clean up a feature branch to only show code changes for code review?▼

To clean up a feature branch for code review, apply a filter to remove planning-related commits such as .planning/ directories. This produces a code-focused PR that preserves essential code commits while ensuring deterministic execution.

What happens if I filter a branch that has no planning artifacts?▼

If you filter a branch with no planning artifacts, the process gracefully handles the branch without causing errors. It preserves essential code commits and ensures deterministic execution, leaving your code changes intact for review.

Can I use this branch cleanup method within my standard git workflow?▼

Yes, you can use this branch cleanup method within standard git workflows to keep history meaningful and review-friendly. It cleanly filters out .planning/ and other planning-related commits from the target branch to produce a code-focused PR.

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
VYRE-StudiosVYRE-Studios

commit-push-pr

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

Official
Intermediate
markus41markus41
1

gitworfkflows

Manage Git branching, commits, rebasing, and pull requests.

Community
Basic
maggitmaggit

rebase

Plan and execute non-interactive git rebase operations with safety checks.

Community
Intermediate