gsd-pr-branch

Filter planning commits from the current branch to create a clean PR branch.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rkz91/coco --skill gsd-pr-branch-rkz91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-pr-branch
Source: https://github.com/rkz91/coco/tree/main/systems/gsd/skills/gsd-pr-branch
Command: npx skills add https://github.com/rkz91/coco --skill gsd-pr-branch-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The current development process often results in PR diffs that include planning artifacts (.planning/ commits, PLAN.md, SUMMARY.md, STATE.md). This skill filters out planning commits to deliver a clean code-focused PR.

Core Features & Use Cases

  • Pruning planning artifacts: Removes commits that introduce or modify planning files, keeping diffs focused on code changes.
  • Deterministic PR branch creation: Produces a branch ready for review from the current branch without planning noise.
  • Use Case: When preparing a feature branch for a code review, run this skill to ensure only implementation changes are visible.

Quick Start

Run the pr-branch workflow to filter out .planning/ commits from the current 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 exclude planning commits from a git branch before creating a pull request?

To exclude planning commits from a git branch, you can filter out commits containing the .planning/ marker to produce a clean PR branch. This deterministic workflow preserves only code changes, ensuring planning artifacts like PLAN.md do not appear in diffs.

How do I remove PLAN.md, SUMMARY.md, and STATE.md files from my PR diff?

Removing PLAN.md, SUMMARY.md, and STATE.md files from your PR diff is achieved by pruning commits that introduce or modify these planning artifacts. The workflow filters commits with the .planning/ marker, leaving only implementation changes for code review.

What is a deterministic pr-branch workflow for filtering planning artifacts?

A deterministic pr-branch workflow for filtering planning artifacts is a process that systematically removes commits containing the .planning/ marker from your current branch. It produces a clean, code-focused branch ready for review without manual intervention.

Does this planning commit filter work with existing feature and bugfix branches?

Yes, this planning commit filter works with existing feature and bugfix branches. It processes the current branch to remove planning noise, making it suitable for standard code-review workflows where only implementation changes should be visible.

Can I run this branch cleanup workflow without installing additional dependencies?

You can run this branch cleanup workflow without additional dependencies, as it operates directly on the current branch. It requires no external components, filtering the .planning/ commits to generate a clean PR branch automatically.

Why does my code review diff include planning artifacts instead of just code changes?

Your code review diff includes planning artifacts because standard git branches retain all commits, including those modifying .planning/ files. Applying a filtering workflow removes these planning commits, ensuring the PR diff displays only code changes.