skills.rest
mcampbellr
mcampbellrCOMMUNITY
Explore all skills by this author →
Website𝕏@mariocampbellrGitHub

gsd-pr-branch

Remove .planning/ commits from a branch to create a clean pull request branch.

Updated Apr 22, 2025
Search Tags:#git#code review#pull request#branch management#commit filtering
One-click install
npx skills add https://github.com/mcampbellr/.dotfiles --skill gsd-pr-branch-mcampbellr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-pr-branch
Source: https://github.com/mcampbellr/.dotfiles/tree/main/claude/.claude/skills/gsd-pr-branch
Command: npx skills add https://github.com/mcampbellr/.dotfiles --skill gsd-pr-branch-mcampbellr

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 branch by filtering out non-code commits from the .planning/ directory, ensuring a focused review experience.

Core Features & Use Cases

  • Automated Branch Cleaning: Removes .planning/ commits from the current branch, creating a clean state for code review.
  • Enhanced Code Review: Facilitates a more focused code review by removing irrelevant planning artifacts.
  • Use Case: When preparing a pull request, this Skill can be used to ensure that only code changes are included, improving the efficiency of the review process.

Quick Start

Use the gsd-pr-branch skill to create a clean PR branch by running '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 commits from a git branch before a pull request?▼

You can clean a pull request branch by automating the removal of .planning/ directory commits. This filtering process ensures that only relevant code changes are included for a focused code review.

What is the best way to filter out non-code files from a PR branch?▼

The best way to filter non-code files from a PR branch is by removing .planning/ directory commits. This ensures reviewers only see relevant code changes, improving the efficiency of the review process.

Can I use bash commands to clean up a git branch for code review?▼

Yes, you can use Bash commands to clean a git branch for code review. The process requires repository access and the ability to execute Bash scripts to automate the removal of .planning/ commits.

Why should I exclude planning artifacts from my pull requests?▼

Excluding planning artifacts from pull requests provides a focused review experience. Removing these non-code commits ensures reviewers concentrate solely on the actual code changes being proposed.

Does branch cleaning affect the original commits in the repository?▼

Branch cleaning removes .planning/ commits from the current branch to create a clean state for code review. It operates on the branch level to ensure only code changes are included in the pull request.

Related Skills

Explore More Software Engineering Skills→
cill-i-amcill-i-am

finishing-a-development-branch

Verify tests and present merge, PR, or cleanup options for Git branches.

Community
Advanced
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
lgwanailgwanai
4

gsd-pr-branch

Create a pull request branch excluding .planning/ commits from the diff.

Community
Intermediate
maggitmaggit

rebase

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

Community
Intermediate