Filter .planning/ commits from a branch to produce a clean PR diff.
npx skills add https://github.com/onelee85/my-skills --skill gsd-pr-branch
Please help me install this Agent Skill. Skill: gsd-pr-branch Source: https://github.com/onelee85/my-skills/tree/main/gsd-pr-branch Command: npx skills add https://github.com/onelee85/my-skills --skill gsd-pr-branch
Filter out .planning/ commits from the current branch to produce a clean PR diff, so code reviews focus on the actual changes.
Create a clean PR branch from the current branch by filtering out .planning/ commits
High-intent search queries and answers about installing and using this skill.
Filtering planning artifacts from a PR diff involves rewriting your feature branch to drop `.planning/` commits. This process ensures files like PLAN.md and SUMMARY.md are excluded while keeping all actual code changes intact for accurate review.
Your code review includes these planning files because they exist in your branch history. Filtering out `.planning/` commits removes PLAN.md, SUMMARY.md, and STATE.md from the diff, ensuring reviews focus strictly on actual code changes.
The best way to clean up a feature branch is to filter out planning artifacts using a deterministic workflow. This rewrites the branch to drop `.planning/` commits, producing a clean PR diff that excludes planning artifacts while preserving code changes.
Yes, filtering out planning commits preserves your code changes. The workflow specifically targets and drops `.planning/` artifacts while keeping all code modifications intact, ensuring the final PR diff remains accurate for code review.
Yes, you can remove planning artifacts without losing code history. The workflow rewrites the branch to drop only `.planning/` commits while preserving all code changes, ensuring teams maintain clean histories on feature branches for review.
lgwanaiCreate a pull request branch excluding .planning/ commits from the diff.
SamyakJhaveriPush a local feature branch and create a GitHub pull request.
wildbitcaStandardize Git workflows with conventional commits, branch prefixes, and PR checks.
maggitPlan and execute non-interactive git rebase operations with safety checks.
