skills.rest
DuySeu
DuySeuCOMMUNITY
Explore all skills by this author →
GitHub

gsd-pr-branch

Filter .planning/ commits from the current Git branch to create a PR-ready branch with code-only changes.

1|Updated Aug 17, 2025
Search Tags:#automation#git#code-review#pull-request#branch-cleanup#planning-artifacts
One-click install
npx skills add https://github.com/DuySeu/StockMind --skill gsd-pr-branch-duyseu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-pr-branch
Source: https://github.com/DuySeu/StockMind/tree/main/.agent/skills/gsd-pr-branch
Command: npx skills add https://github.com/DuySeu/StockMind --skill gsd-pr-branch-duyseu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a clean PR branch by filtering out .planning/ commits so that code reviewers only see relevant changes.

Core Features & Use Cases

  • Filter out .planning/ commits from the current branch to produce a PR-friendly diff.
  • Preserve all code changes while removing planning artifacts, ensuring a clean review experience.
  • Use case: when preparing a feature branch for review, avoid noise from planning documents & artifacts.

Quick Start

Generate a clean PR branch from the current branch by filtering out any .planning/ commits.

Frequently Asked Questions about gsd-pr-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I filter out planning artifacts from a git branch for code review?▼

To filter planning artifacts from a git branch, this Skill removes .planning/ commits to produce a PR-ready branch. It preserves all code changes while excluding planning documents, ensuring reviewers only see relevant code diffs.

How do I remove .planning/ files from my pull request diff?▼

You can remove .planning/ files from your pull request diff by running the integrated pr-branch workflow. It isolates code changes from planning artifacts, creating a clean branch that prevents planning documents from cluttering the code review process.

What is the best way to create a clean PR branch without planning noise?▼

The best way to create a clean PR branch without planning noise is to use a dedicated branch cleanup workflow. It automatically strips .planning/ commits from the current branch, leaving a PR-friendly diff containing only code modifications for review.

Can I separate planning documents from code changes in my git workflow?▼

Yes, you can separate planning documents from code changes in your git workflow. This Skill executes a pr-branch workflow that filters out .planning/ commits, allowing you to isolate code changes and prepare a clean pull request branch for reviewers.

Why should I exclude .planning/ commits before submitting a pull request?▼

You should exclude .planning/ commits before submitting a pull request to provide a clean review experience. Filtering planning artifacts ensures code reviewers only evaluate relevant code changes, preventing planning documents from distracting or cluttering the diff.

Does this branch cleanup workflow preserve my code changes when filtering commits?▼

Yes, this branch cleanup workflow preserves all code changes when filtering commits. It specifically targets and removes .planning/ artifacts, ensuring your PR-ready branch retains all functional code modifications while eliminating planning document noise from the diff.

Related Skills

Explore More Software Engineering Skills→
tinner-deinnotinner-deinno

gsd-pr-branch

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

Community
Intermediate
0xdeafcafe0xdeafcafe

drive-pr

Resolve trusted GitHub PR feedback, fix CI failures, and update descriptions.

Community
Advanced
friedbotstudiofriedbotstudio
5

commit

Stage and commit baseline workflow changes with archive synchronization and consent checks.

Official
Advanced
DektoraDektora

pr-branch

Create clean pull request branches by filtering spec-only commits.

Official
Advanced