branch-surgery-pr-split
Branch Surgery PR Split
Overview
Use this skill to turn a risky monolithic branch into a safe, auditable set of scoped PRs. Treat topology as a decision, not a default recipe, and collaborate with the user before executing branch surgery.
Workflow
- Quantify branch shape before proposing solutions.
- Always present the top two topology options with explicit tradeoffs.
- Collaborate with the user to select one topology.
- Produce a decision-complete split plan.
- Execute with safety refs and strict scope boundaries.
- Run parity and completeness audits.
- Remediate drift and generate PR metadata.
Step 1: Quantify Branch Shape
More from liatrio-labs/ai-prompts
git-commit-conventional
Create Conventional Commit messages and execute safe git commits from working tree changes. Use when users ask to create a commit, write a conventional commit message, split broad changes into multiple commits, stage only parts of files, run pre-commit before committing, or perform a quick commit-time quality review with severity guardrails.
24create-pull-request
Generate a reviewer-ready pull request or merge request title and description from branch changes. Use when a user asks to draft PR/MR content, summarize branch deltas against a base branch, or optionally create the PR with gh/glab after approval.
23create-mermaid-diagrams
Create, validate, and repair Mermaid diagrams for technical documentation with a deterministic CLI feedback loop. Use when an AI needs to create Mermaid diagrams, improve Mermaid diagram quality, validate Mermaid fences in markdown, diagnose Mermaid rendering failures, or fix Mermaid syntax and formatting issues.
21liatrio-brand-guidelines
Applies Liatrio brand guidelines to UI design, brand audits, and asset selection. Use when users request Liatrio styling, logo variants, typography or color decisions, visual polish, or formal brand compliance checks.
21uv-usage
Provides concise guidance for using uv (Python package manager), including project workflows, pip-compatible commands, Python version management, and PEP 723 inline script dependencies. Use when users mention uv, uv run, inline dependencies, PEP 723, or Python dependency/project management.
16tilt-dev
Manage local development environments with Tilt. Use when working with projects that run services via Tilt (indicated by presence of Tiltfile), including checking service status, viewing logs, troubleshooting connectivity issues, or managing the Tilt stack. Essential for projects using Tiltfile with local_resource for orchestrating backend, frontend, and other services.
15