skills.rest
zcaceres
zcaceresCOMMUNITY
Explore all skills by this author →
Website𝕏@zachcaceresGitHub

pr

Checkpoint local diffs into sequential branches for stacked pull requests.

7|Updated May 28, 2026
Search Tags:#automation#git#github#code-review#pull-request#stacked-prs
One-click install
npx skills add https://github.com/zcaceres/skills --skill pr-zcaceres
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/zcaceres/skills/tree/main/skills/pr
Command: npx skills add https://github.com/zcaceres/skills --skill pr-zcaceres

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires zod, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill solves the problem of fragmented, messy pull request workflows by enabling a stacked PR approach, allowing you to build and ship logical slices of work locally before publishing them as a cohesive, reviewable stack.

Core Features & Use Cases

  • Stacked PR Workflow: Automatically checkpoints your current diff into a new branch, maintaining a clean stack of PRs that are published together.
  • Annotatable Review: Generates numbered Markdown review documents with exact patches, allowing for structured, colorized feedback via git-delta.
  • Automated Nudge: Includes an optional, non-blocking hook that monitors your diff size and nudges you to checkpoint your work into a focused PR before it becomes unwieldy.

Quick Start

Use the pr skill to checkpoint your current changes as a new stacked slice with the description 'add authentication middleware'.

Frequently Asked Questions about pr

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

FAQPage Schema
What are stacked pull requests and when do I need them for code review?▼

Automating stacked PR creation checkpoints local diffs into sequential branches, eliminating messy pull request workflows. It maintains a clean stack of PRs published together, allowing you to build and ship logical slices of work locally before publishing them as a cohesive, reviewable stack.

How do I create a stacked PR from my current git diff?▼

You need git-stack or gh CLI integration to synchronize local stack state with GitHub pull request metadata. These tools facilitate bottom-up merging and atomic code reviews by connecting your local stacked branches with remote GitHub pull request metadata.

Does this stacked PR workflow support jujutsu branches and GitHub CLI?▼

Yes, stacked PRs generate numbered Markdown review documents with exact patches. This allows for structured, colorized feedback via git-delta, providing an annotatable review format for precise code review feedback.

What is the best way to prevent a pull request diff from becoming unwieldy?▼

The best way to prevent unwieldy pull request diffs is using an automated, non-blocking hook that monitors diff size. It nudges you to checkpoint your work into a focused, atomic PR before the changes become too large for effective code review.

Can I review stacked PR patches with colorized feedback in Markdown?▼

Yes, stacked PRs generate numbered Markdown review documents with exact patches. This allows for structured, colorized feedback via git-delta, providing an annotatable review format for precise code review feedback.

Related Skills

Explore More Software Engineering Skills→
wyattjohwyattjoh
1

pr-status

Visualize GitHub pull request stacks and identify stale local branches.

Community
Intermediate
arittrarittr
19

using-git-spice

Manage stacked Git branches and Change Requests with git-spice commands.

Community
Advanced
cloud-native-toolscloud-native-tools

code-review

Standardize code reviews with git-delta diff visualization and structured feedback.

Official
Advanced
jkomorosjkomoros
9

land-branch

Rebase a feature branch onto main and merge via pull request.

Community
Intermediate