pr-staged-merge-planlisted

Use when a large pull request should be merged and deployed in safe parts instead of all at once. Analyzes every commit in the PR, groups them into atomic logical units that each ship independently without downtime, orders the units by dependency and rollback risk, proposes squashes for a clean human-readable history, and proposes corrected subjects for vague or inaccurate commit messages. Read-only — it proposes the plan and never rewrites history, pushes, or merges.
pekral/cursor-rules · ★ 7 · Code & Development · score 79

Install: claude install-skill pekral/cursor-rules

## Constraints - Apply `@rules/git/general.mdc` — every proposed commit subject follows *Commit Messages* (English, `type(scope): short description`, lowercase, allowed types only, no trailing period) and every proposed unit follows *One phase = one commit*. - **Read-only.** Never run `git rebase`, `git commit --amend`, `git cherry-pick`, `git reset`, `git push`, `gh pr merge`, or `gh pr edit`. This skill produces a plan; a human or a follow-up skill executes it. - Load PR context only through `skills/code-review-github/scripts/load-issue.sh <NUMBER|URL>`. Never call `gh pr view` / `gh api /repos/.../pulls/...` directly; fall back to the GitHub MCP server only when the loader is unavailable (exit code 2/3). Local `git log` / `git diff` reads against the loaded base and head refs are expected and allowed. - Merging a unit is owned by `@skills/merge-github-pr/SKILL.md`; interactive-rebase, conflict, and force-with-lease mechanics are owned by `@skills/git-workflow/SKILL.md`. Reference them — do not restate them. - **Commit-level splitting inside one PR is owned by the CR gate, not by this skill.** The **Commit Split & Atomic Deployability Gate** (`@rules/code-review/general.mdc` *Commit Split & Atomic Deployability Proposal — canonical walk-through*) runs on every code review and raises a **Critical** finding with a commit-level repartition of the PR's own history. This skill is the on-demand deeper plan: it splits the work into **several pull requests**, each with its own revi