skills.rest
zerAda
zerAdaCOMMUNITY
Explore all skills by this author →
GitHub

gsd-pr-branch

Filter non-code commits from a branch by excluding .planning/ directories.

Updated Jan 21, 2026
Search Tags:#code review#code organization#commit filtering#PR branch cleaning#branch preparation
One-click install
npx skills add https://github.com/zerAda/RestaurantAgentAutomation --skill gsd-pr-branch-zerada
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-pr-branch
Source: https://github.com/zerAda/RestaurantAgentAutomation/tree/main/.agent/skills/gsd-pr-branch
Command: npx skills add https://github.com/zerAda/RestaurantAgentAutomation --skill gsd-pr-branch-zerada

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of creating a clean pull request (PR) branch by filtering out .planning/ commits, ensuring that reviewers focus only on code changes.

Core Features & Use Cases

  • PR Branch Cleaning: Filters out non-code commits from .planning/ directory to create a clean PR branch.
  • Code Review Readiness: Ensures that code reviews are not cluttered with irrelevant planning artifacts.
  • Use Case: When you want to submit a PR for code review, this Skill helps you prepare a clean branch that only contains code-related changes.

Quick Start

Run the 'gsd-pr-branch' Skill to prepare a clean PR branch for code review.

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 non-code commits before creating a pull request?▼

To filter out non-code commits before creating a pull request, you can automate branch cleaning to exclude specific directories like .planning/. This ensures your PR branch contains only code-related changes for reviewers.

How do I exclude .planning/ artifacts from my PR branch?▼

Excluding .planning/ artifacts from your PR branch involves filtering out non-code commits specific to that directory. This prepares a clean branch so code reviewers focus strictly on code changes.

What is the best way to prepare a clean PR branch for code review?▼

The best way to prepare a clean PR branch for code review is to automate the filtering of non-code directories. This removes planning artifacts, ensuring only relevant code changes are visible to reviewers.

Can I automate PR branch cleaning to remove planning directories?▼

Yes, you can automate PR branch cleaning to identify and exclude specific directories such as .planning/. This process automatically generates a clean branch containing only code-related commits.

Why does my pull request branch include irrelevant planning files?▼

Your pull request branch includes irrelevant planning files because non-code commits from directories like .planning/ are mixed into your branch history. Filtering these commits solves this clutter issue.

Does this branch cleaning process require any specific dependencies?▼

No, this branch cleaning process does not require any specific dependencies to function. It runs independently using scripts to identify and filter out non-code commits from your branch.

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
SamyakJhaveriSamyakJhaveri

pr

Push a local feature branch and create a GitHub pull request.

Community
Intermediate
coco-researchcoco-research
264

gsd-pr-branch

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

Community
Intermediate
Knuckles-TeamKnuckles-Team
2

git-advanced

Automate Git history fixes using rebase, cherry-pick, and bisect workflows.

Official
Advanced