skills.rest
MINT-IA
MINT-IAOFFICIAL
Explore all skills by this author →
GitHub

gsd-pr-branch

Filter planning commits from a Git branch to produce a clean PR branch.

Updated Jan 25, 2026
Search Tags:#git#workflow#branch#pr#code-review#planning-artifacts
One-click install
npx skills add https://github.com/MINT-IA/MINT --skill gsd-pr-branch-mint-ia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-pr-branch
Source: https://github.com/MINT-IA/MINT/tree/main/.claude/skills/gsd-pr-branch
Command: npx skills add https://github.com/MINT-IA/MINT --skill gsd-pr-branch-mint-ia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Filter out planning artifacts from PR diffs
  • Works with local feature branches and default target main
  • Integrates with existing pr-branch workflow across Git-based projects

Quick Start

Execute the pr-branch workflow against your current branch to 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 remove planning commits from a git branch, you can use a pr-branch workflow to filter out .planning/ artifacts. This produces a clean PR branch where reviewers see only the actual code changes.

What is the best way to keep planning artifacts out of my git PR diffs?▼

Keeping planning artifacts out of git PR diffs is achieved by filtering out .planning/ commits from your current feature branch. This ensures the code review process focuses solely on code changes.

Can I use the pr-branch workflow with a target branch other than main?▼

The pr-branch workflow requires a defined target branch for filtering, defaulting to main. It works with local feature branches to produce clean PR branches across Git-based projects.

How does filtering planning commits improve the code review workflow?▼

Filtering planning commits improves code review by ensuring diffs show only code changes across feature or release branches. This removes noise from planning artifacts so reviewers focus on implementation.

What types of git commits are excluded when creating a clean PR branch?▼

When creating a clean PR branch, commits containing .planning/ artifacts are excluded from the final diff. This filters out planning documents while preserving the actual code modifications.

Do I need any special git dependencies to filter planning commits from my feature branch?▼

No special dependencies are required to filter planning commits from your feature branch. You simply execute the pr-branch workflow against your current branch to produce the clean PR output.

Related Skills

Explore More Software Engineering Skills→
zoraxlzoraxl
3

rebase-onto-main

Rebase local feature branches onto the default base branch with conflict resolution and audit reports.

Community
Advanced
apeejay-educationapeejay-education

ship

Automate release workflows from branch merge to PR creation.

Official
Advanced
AmidVoshakulAmidVoshakul

find-bugs

Identify security vulnerabilities and code quality issues in local git branch diffs.

Community
Advanced
maggitmaggit

rebase

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

Community
Intermediate