skills.rest
nnexai
nnexaiCOMMUNITY
Explore all skills by this author →
GitHub

gsd-pr-branch

Filter .planning/ directory commits from the current git branch.

1|Updated Apr 4, 2026
Search Tags:#automation#git#workflow#cleanup#pull-request#gsd
One-click install
npx skills add https://github.com/nnexai/git-stacks --skill gsd-pr-branch-nnexai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-pr-branch
Source: https://github.com/nnexai/git-stacks/tree/main/.codex/skills/gsd-pr-branch
Command: npx skills add https://github.com/nnexai/git-stacks --skill gsd-pr-branch-nnexai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the issue of cluttered pull request diffs caused by GSD-generated planning artifacts like PLAN.md, SUMMARY.md, and STATE.md, which are irrelevant to code review.

Core Features & Use Cases

  • Automated Cleanup: Automatically filters out .planning/ commits from your current branch.
  • Reviewer Focus: Ensures that code reviewers see only actual code changes rather than project management metadata.
  • Use Case: After completing a complex feature development using GSD workflows, run this skill to prepare a clean, professional branch ready for merging into the main codebase.

Quick Start

Invoke the skill by typing $gsd-pr-branch in your terminal to automatically filter planning commits and prepare your current branch for a pull request.

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 files from my git branch before creating a pull request?▼

To clean up your pull request, filter out .planning/ directory commits from your current git branch. This removes GSD-generated artifacts like PLAN.md and SUMMARY.md so reviewers only see actual code changes.

Why does my pull request diff include PLAN.md and SUMMARY.md files?▼

Your pull request includes these files because GSD workflows generate planning artifacts in the .planning/ directory and commit them to your branch. You can filter out these non-code planning files to ensure reviewers focus solely on the code changes.

What is the best way to clean up GSD planning artifacts from version control history?▼

The best way to clean up GSD planning artifacts is to automatically filter .planning/ directory commits from your current git branch. This removes non-code planning files and produces a clean state for your pull requests.

Do I need a initialized GSD project structure to filter out planning commits?▼

Yes, you need a properly initialized GSD project structure and git access. The filtering process relies on identifying the .planning/ directory within your repository to accurately separate non-code planning files from actual code changes.

Can I automate the cleanup of .planning/ directory commits in my git workflow?▼

Yes, you can automate the cleanup of .planning/ directory commits in your git workflow. By running an automated filtering process on your current branch, you can prepare a professional, clean state ready for merging into the main codebase without manual file removal.

Related Skills

Explore More Software Engineering Skills→
oaustegardoaustegard
137

versioning-skills

Initialize Git repositories and commit changes for skill directories.

Community
Basic
zerAdazerAda

gsd-pr-branch

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

Community
Intermediate
electroheadfxelectroheadfx
4

gsd-pr-branch

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

Community
Intermediate
maggitmaggit

rebase

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

Community
Intermediate