mergekit

Sets up GitHub pull requests for local review and merges them after explicit human confirmation.

1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/mimukit/skills --skill mergekit-mimukit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mergekit
Source: https://github.com/mimukit/skills/tree/main/skills/mergekit
Command: npx skills add https://github.com/mimukit/skills --skill mergekit-mimukit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing and merging pull requests involves repetitive manual work: checking out branches, wiring up worktrees, installing dependencies, gathering review threads and CI status, and then safely merging without bypassing human judgment. This Skill automates the setup and execution while keeping every merge behind an explicit per-PR human confirmation. ## Core Features & Use Cases - Review workspace setup: Pulls any open PR into a git worktree (adopting an existing one when present), installs project dependencies, and prints a review pack with commits, diff stats, unresolved review threads, CI status, and behind/ahead counts. - Gated merging: Merges a PR only after a named, per-PR human confirmation, handles stacked PR cascades with full enumeration, and hands off issue closing and tracker sync to issuekit. - Review feedback servicing: The fix mode gathers review comments and failing CI on your own PR, triages each item as fix/decline/ask against project conventions, implements fixes, and replies to every thread. - Use Case: Say "pull PR #34 down so I can test it" and get a running worktree plus a complete review pack; then say "merge #34" to land it after confirmation. ## Quick Start Ask the agent to pull PR #34 down into a worktree and set it up so you can review and test it locally.

Frequently Asked Questions about mergekit

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

FAQPage Schema
How do I review a GitHub pull request locally?

Run the start mode with the PR number, for example "pull PR #34 down so I can test it". It fetches the head branch into a git worktree, installs the project's dependencies, and prints a review pack with commits, diff stats, unresolved review threads, and CI status.

How do I address review comments on my GitHub PR?

Use the fix mode with your PR number. It gathers unresolved review threads and failing checks, triages each item as fix, decline, or ask against the repo's conventions, implements the accepted fixes, pushes, and replies to every thread.

Can a pull request be merged automatically without confirmation?

No. Every merge requires an explicit, per-PR confirmation from a human who just reviewed that PR. Green CI, approvals, and resolved threads are inputs to the decision, never the decision itself, and batch merges are refused.

Does it support stacked pull requests?

Yes. It detects when a PR's base is another feature branch, lists the full cascade in merge order before confirming, and merges the stack bottom-up using gh stack merge. After a cascade, each merged layer's issue is closed individually.

What happens with pull requests from forks?

Fork PRs are read-only: you can review and merge them, but you cannot push fixes to the contributor's branch. The skill creates a local pr-<n>-<slug> branch for the worktree and states the read-only limitation at setup time.

Why does creating a worktree for a PR branch fail?

Git allows a branch to be checked out in exactly one worktree, so creating a second one fails if the branch already has one. The skill avoids this by looking up and adopting the existing worktree before ever creating a new one.