pr

Create bug-fix branches with git worktrees for parallel fixes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/krystophny/prompts --skill pr-krystophny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/krystophny/prompts/tree/main/skills/pr
Command: npx skills add https://github.com/krystophny/prompts --skill pr-krystophny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate bug fixes across multiple branches by creating dedicated work contexts using git worktrees to keep changes isolated and organized.

Core Features & Use Cases

  • Create one or more bug-fix branches from current changes or from main
  • Support parallel workstreams via git worktrees for concurrent fixes
  • Provide a clear workflow for naming, testing, and PR creation to streamline reviews

Quick Start

Create a new bug-fix branch from your current changes or origin/main, optionally naming multiple branches to run in parallel.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I work on multiple bug fixes in parallel without stashing my current changes?

You can use git worktree to create dedicated work contexts for each bug fix branch, allowing you to run parallel workstreams from your current changes or origin/main while keeping everything isolated.

What is the best way to create multiple bug-fix branches from origin/main simultaneously?

Creating multiple bug-fix branches from origin/main is best handled by generating separate git worktrees, which scaffolds isolated workstreams for concurrent fixes and keeps them organized for review.

Can I create a new git worktree starting from my uncommitted current changes?

Yes, you can create a new bug-fix branch using a git worktree that applies directly to your current changes, scaffolding the workflow to keep those fixes isolated and ready for review.

How does git worktree management help with branch creation for concurrent fixes?

Git worktree management scaffolds branch creation by establishing isolated workstreams, allowing you to organize multiple concurrent fixes with optional naming to streamline the review process.

Does this parallel branch workflow provide a process for naming and testing fixes before review?

Yes, the workflow scaffolding includes a clear process for naming, testing, and PR creation, ensuring your isolated bug fixes are organized and prepared for review immediately after branch creation.

When should I not use git worktrees for bug fixes?

Git worktrees are not ideal if you only need a single quick fix or lack disk space for multiple working directories, as the orchestration is designed for managing multiple parallel workstreams simultaneously.