gsd-pr-branch

Remove .planning/ commits from a git branch for clean pull requests.

Updated May 3, 2026

Search Tags:#code review #git workflow #commit filtering #PR branch cleanup #clean branch

Ready to run

npx skills add https://github.com/ThiagoVitale/endless-crystal --skill gsd-pr-branch-thiagovitale

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-pr-branch
Source: https://github.com/ThiagoVitale/endless-crystal/tree/main/.codex/skills/gsd-pr-branch
Command: npx skills add https://github.com/ThiagoVitale/endless-crystal --skill gsd-pr-branch-thiagovitale

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the issue of cluttered pull request diffs caused by unnecessary planning artifacts like PLAN.md, SUMMARY.md, and STATE.md.

Core Features & Use Cases

Commit Filtering: Removes .planning/ commits from the current branch to create a clean state for code reviews.
Code Review Readiness: Ensures that code reviewers focus solely on code changes and not on planning artifacts.
Use Case: Use this Skill to generate a clean pull request branch before initiating a code review process, making the diff more readable and efficient.

Quick Start

Trigger the skill by typing $gsd-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 artifacts from a pull request diff?▼

You can remove planning artifacts from a pull request diff by filtering out .planning/ commits. This Skill creates a clean PR branch state so reviewers focus solely on code changes instead of PLAN.md or SUMMARY.md files.

How do I clean up a git branch before code review?▼

To clean up a git branch before code review, you need to remove unnecessary .planning/ commits. This Skill filters those commits to generate a clean pull request branch, making the diff more readable and efficient.

Why are planning files cluttering my pull request commits?▼

Planning files like PLAN.md, SUMMARY.md, and STATE.md clutter pull request commits because they are tracked in the .planning/ directory. Removing these planning artifacts ensures code reviewers focus only on the actual code changes.

Can I exclude .planning/ directory commits from my git workflow?▼

Yes, you can exclude .planning/ directory commits from your git workflow. This Skill requires a git repository containing a .planning/ directory and removes those specific commits to create a clean pull request state.

Do I need a .planning/ directory to use this commit filtering approach?▼

Yes, you need a git repository with a .planning/ directory to use this commit filtering approach. The Skill specifically targets and removes commits associated with the .planning/ folder to prepare a clean branch for code review.

What is the best way to improve code review focus by excluding non-code commits?▼

The best way to improve code review focus by excluding non-code commits is to filter out .planning/ artifacts. This process removes planning commits from the current branch, ensuring the pull request diff contains only relevant code modifications.