collect-for-pr

Batch subdirectory worktree commits into a single pull request.

6|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/itsgrimetime/melee-decomp --skill collect-for-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: collect-for-pr
Source: https://github.com/itsgrimetime/melee-decomp/tree/main/.claude/skills/collect-for-pr
Command: npx skills add https://github.com/itsgrimetime/melee-decomp --skill collect-for-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collects pending worktree commits and batches them into a pull request for review, reducing review overhead and speeding integration.

Core Features & Use Cases

  • Batch commits from subdirectory worktrees into a single PR to streamline reviews.
  • Supports a dry-run preview to validate batch composition before PR creation.
  • Creates a branch, cherry-picks commits, and opens a PR with an organized commit list.
  • Handles conflicts gracefully and defers unresolved commits for future batches.

Quick Start

Always start with a dry-run using melee-agent worktree collect --source-dir <subdir> --dry-run to preview the batch before creating a PR.

Frequently Asked Questions about collect-for-pr

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

FAQPage Schema
How do I batch commits from git worktrees into a single pull request?

To batch commits from git worktrees into a single pull request, use a tool that automatically collects pending worktree commits, cherry-picks them onto a new branch, and opens an organized PR. This reduces review overhead and speeds up integration.

Can I preview grouped commits before creating a pull request?

Yes, you can preview grouped commits before creating a pull request by running a dry-run command. This validates your batch composition and shows exactly which worktree commits will be included before the actual PR creation.

What happens to commit batching when there are merge conflicts?

When commit batching encounters merge conflicts during cherry-picking, the process handles conflicts gracefully by deferring unresolved commits. These overflow commits are skipped and saved for inclusion in future PR batches.

When should I batch multiple worktree commits into one PR?

You should batch multiple worktree commits into one PR when your subdirectory worktrees accumulate 4-7 or more pending commits. Grouping them together streamlines code reviews and reduces integration overhead.

Does git worktree commit batching handle branch naming and cleanup?

Yes, git worktree commit batching handles branch naming and cleanup. It supports optional custom branch naming during creation and performs post-PR cleanup to keep your local worktree environment organized after review monitoring.