ferrox-pr-branch

Create a pull-request branch by filtering out .planning commits.

21|9|Updated Jul 21, 2026

Search Tags:#git #pull request #review workflow #branch cleanup #commit filtering

Ready to run

npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-pr-branch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ferrox-pr-branch
Source: https://github.com/FerroxLabs/ferrox-factory/tree/main/skills/ferrox-pr-branch
Command: npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-pr-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates a clean pull-request branch by removing .planning commits, so reviewers can focus on real code changes instead of planning artifacts.

Core Features & Use Cases

PR branch cleanup: Rewrites or filters branch history to exclude planning-related commits.
Review-friendly diffs: Keeps PLAN.md, SUMMARY.md, and STATE.md noise out of the pull request.
Use Case: When a feature branch contains both implementation work and Ferrox planning updates, use this Skill to prepare a reviewer-ready branch with only the meaningful code changes.

Quick Start

Use the ferrox-pr-branch skill to create a clean pull-request branch from my current branch targeting main.

Frequently Asked Questions about ferrox-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 creating a pull request?▼

To remove planning commits from a git branch before creating a pull request, this Skill filters your current branch to exclude .planning artifacts like PLAN.md and SUMMARY.md. It rewrites the branch history, resulting in a clean PR diff containing only production code changes for reviewers to evaluate.

How do I exclude PLAN.md and STATE.md files from a pull request diff?▼

Excluding PLAN.md and STATE.md files from a pull request diff is achieved by filtering out .planning commits from your feature branch history. This ensures these planning artifacts do not appear in the final review diff, allowing reviewers to focus solely on the meaningful code changes.

What is the best way to clean up a feature branch for code review?▼

The best way to clean up a feature branch for code review is to filter out planning-related commits and artifacts. This Skill creates a separate, review-friendly pull-request branch by removing .planning noise, ensuring reviewers see only the implementation work without being distracted by planning updates.

Does this branch cleanup process rewrite existing git commit history?▼

Yes, this branch cleanup process rewrites existing git commit history to remove .planning artifacts. By manipulating the branch history and cleaning up the commit sets, it ensures that planning files like PLAN.md, SUMMARY.md, and STATE.md are completely excluded from the final pull request diff.

Can I create a clean PR branch targeting main while keeping planning files in my workspace?▼

Yes, you can create a clean PR branch targeting main while keeping planning files in your workspace. This Skill filters the .planning commits from the branch history used for the pull request, allowing you to maintain your planning artifacts locally without including them in the reviewer-facing diff.