gsd-pr-branch

Creates a clean pull request branch by filtering out .planning/ commits.

2|Updated Mar 7, 2025
One-click install
npx skills add https://github.com/AbdelrhmanUZaki/KnowledgeNuggets --skill gsd-pr-branch-abdelrhmanuzaki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-pr-branch
Source: https://github.com/AbdelrhmanUZaki/KnowledgeNuggets/tree/main/2-setup/shared/codex/skills/gsd-pr-branch
Command: npx skills add https://github.com/AbdelrhmanUZaki/KnowledgeNuggets --skill gsd-pr-branch-abdelrhmanuzaki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull request diffs often get cluttered with GSD planning artifacts like PLAN.md, SUMMARY.md, and STATE.md commits, making code review harder. This Skill produces a branch containing only code changes so reviewers see a clean diff. ## Core Features & Use Cases - Commit Filtering: Removes .planning/ directory commits from the current branch history before opening a PR. - Review-Ready Branches: Generates a dedicated branch where only source code changes appear in the diff. - Use Case: After finishing a GSD-managed feature with dozens of planning commits, invoke the skill to produce a clean branch and open a pull request that reviewers can read without wading through planning artifacts. ## Quick Start Invoke $gsd-pr-branch on your current feature branch to create a clean PR branch with all .planning/ commits filtered out.

Frequently Asked Questions about gsd-pr-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a clean PR branch without planning commits?▼

Invoke $gsd-pr-branch on your current branch. It filters out all .planning/ directory commits and produces a new branch containing only code changes, ready for a pull request.

How to remove planning artifacts from a git pull request diff?▼

Use this skill to rebuild the branch history excluding .planning/ commits such as PLAN.md, SUMMARY.md, and STATE.md changes. The resulting PR diff shows only source code modifications.

Does gsd-pr-branch work with Codex sub-agents?▼

The skill includes a Codex adapter mapping Claude Code constructs like Task() and AskUserQuestion to spawn_agent and request_user_input. Sub-agent spawning only occurs when the user explicitly requests it; otherwise work is done inline.

What happens if user input is unavailable during the workflow?▼

When request_user_input is rejected or unavailable, the workflow stops and presents questions as a plain-text numbered list, waiting for a reply. It only proceeds without answers when an explicit --auto or --all flag, an approved default, or a documented safe default applies.

When should I not use commit filtering for PR branches?▼

Avoid it when reviewers need the full planning context or when your team tracks planning artifacts in the main history. In those cases, open the PR from the original branch instead of a filtered one.