skills.rest
diShine-digital-agency
diShine-digital-agencyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

shine-pr-branch

Filter planning artifacts from a Git branch for PR-ready code changes.

1|Updated Apr 15, 2026
Search Tags:#automation#git#pr#workflows#code-review#branch-cleanup#planning-artifacts
One-click install
npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-pr-branch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shine-pr-branch
Source: https://github.com/diShine-digital-agency/SHINE-Code-System/tree/main/skills/shine-pr-branch
Command: npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-pr-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Filter planning artifacts from the current Git branch to produce a clean PR-ready branch.

Core Features & Use Cases

  • Filter planning artifacts from the current branch so PR diffs contain only code changes.
  • Integrate with standard code-review workflows to prevent planning notes from leaking into reviews.
  • Use Case: Before opening a PR on a feature branch, remove PLAN.md, SUMMARY.md, and STATE.md changes so reviewers see only code.

Quick Start

Ensure the current branch is checked out and run the branch-cleanup process to generate a PR-ready branch.

Frequently Asked Questions about shine-pr-branch

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

FAQPage Schema
How do I remove planning artifacts from a Git branch before opening a PR?▼

A PR-ready branch is a clean Git branch where planning artifacts like PLAN.md, SUMMARY.md, and STATE.md are filtered out. It ensures code-review workflows only display actual code changes, preventing planning notes from leaking into PR diffs.

Why do my planning notes show up in Git code review diffs?▼

Planning notes show up in Git code review diffs because they are committed to your current feature branch. Running a branch-cleanup process prunes these planning artifacts to generate a clean PR-ready branch for review.

How do I generate a PR-ready branch from my current feature branch?▼

To generate a PR-ready branch, ensure your current feature branch is checked out and execute the branch-cleanup process. This targets the branch and removes planning artifacts, leaving only code changes for the PR.

Can I clean up planning commits without losing my actual code changes?▼

Yes, you can clean up planning commits without losing code changes. The branch-cleanup process specifically targets and prunes planning artifacts like STATE.md from the current Git branch, preserving the actual code modifications for your PR.

What do I need to set up before filtering planning artifacts from my Git branch?▼

To filter planning artifacts from your Git branch, you need the current feature branch checked out and the pr-branch workflow script installed at the designated local path. The process then runs end-to-end using supported Bash and Read tools.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-worktree-create

Create isolated git worktrees for feature branches under .worktrees/.

Community
Advanced
0xdeafcafe0xdeafcafe

drive-pr

Resolve trusted GitHub PR feedback, fix CI failures, and update descriptions.

Community
Advanced
julianobarbosajulianobarbosa
7

Git

Automate Git commit, branch, merge, and PR workflows with GitHub CLI and security checks.

Community
Advanced
Fandry96Fandry96
27

git-advanced-workflows

Rewrite Git commit histories using interactive rebases, cherry-picking, and reflog recovery.

Community
Advanced