skills.rest
corygabrielsen
corygabrielsenCOMMUNITY
Explore all skills by this author →
𝕏@corygabrielsenGitHub

orthogonalize-pr

Analyze pull request commits and generate independent branches for each change set.

1|1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/corygabrielsen/skills --skill orthogonalize-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orthogonalize-pr
Source: https://github.com/corygabrielsen/skills/tree/main/orthogonalize-pr
Command: npx skills add https://github.com/corygabrielsen/skills --skill orthogonalize-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRs often contain multiple unrelated changes, making reviews longer and riskier. Orthogonalize PR identifies independent change sets and isolates them into separate branches to streamline review and merging.

Core Features & Use Cases

  • Dependency-aware branching: clusters commits into orthogonal sets based on dependencies.
  • Targeted review workflow: generate branches containing only the changes relevant to a given feature or fix.
  • Use Case: When a PR adds a bug fix, a refactor, and a documentation update, orthogonalize-pr can propose three separate PRs that can be reviewed and merged independently.

Quick Start

Start with a decomposed PR on a feature branch and run the orthogonalize-pr workflow to produce independent branches ready for review.

Frequently Asked Questions about orthogonalize-pr

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

FAQPage Schema
How do I split a pull request with unrelated changes into separate branches?▼

Splitting a bundled pull request works by analyzing commits, constructing a dependency graph, and generating focused branches that isolate independent change sets for separate review and merging.

What is dependency-aware branching for pull requests?▼

Dependency-aware branching clusters commits into orthogonal sets based on their dependencies, ensuring that unrelated changes in a decomposed pull request are isolated into separate, independently reviewable branches.

How do I separate a bug fix, refactor, and documentation update from a single PR?▼

You can separate a bug fix, refactor, and documentation update from a single PR by running the orthogonalize workflow, which proposes three independent branches mapped from the original bundled commits for isolated merging.

Can I review and merge parts of a pull request independently?▼

Yes, you can review and merge parts of a pull request independently by generating focused branches that contain only the relevant commits, with guidance provided for recombining or splitting them as needed.

When should I decompose a pull request into orthogonal branches?▼

You should decompose a pull request into orthogonal branches when the PR bundles unrelated changes, making reviews longer and riskier, and you need to isolate independent change sets for targeted review workflows.

Related Skills

rajivpantrajivpant
15

synthesis-preflight

Assess git branch readiness with six checks and a go/no-go verdict.

Community
Advanced
edwifiguyedwifiguy
1

git-workflow

Enforce best practices for commits, branches, merges, and pull requests.

Community
Intermediate
amauryconstantamauryconstant
6

osx-modify-artifacts

Modify OpenSpec change artifacts with dependency-aware updates and targeted edits.

Community
Advanced
DektoraDektora

pr-branch

Create clean pull request branches by filtering spec-only commits.

Official
Advanced