← ClaudeAtlas

prepare-prlisted

Author a standardized, structured MR/PR description — Background (need / before / after / related flows), High-Level Design (API/Infra/Schema/UI/Data change table + mermaid sequence), Pitfalls & Regressions — from the branch diff, then open the MR/PR (draft-to-file, adoption-marked) and hand off to /etk:review-mr. Works on GitLab (glab) and GitHub (gh). Use when: opening a merge request or pull request, preparing an MR/PR, writing an MR/PR description, or wrapping a feature/fix before review. Triggers on: prepare-pr, prepare pr, prepare-mr, prepare mr, open PR, open MR, create pull request, create merge request, PR description, MR description, ready for review, ship it
ArieGoldkin/claude-forge · ★ 6 · Code & Development · score 74
Install: claude install-skill ArieGoldkin/claude-forge
# Prepare PR Authors a standardized MR/PR description from the current branch's changes and opens the merge request (GitLab) or pull request (GitHub). Composable: run it standalone when you are ready to open an MR/PR, or call it at the end of `/develop` or `/fix-bug`. It produces the description contract in `${CLAUDE_SKILL_DIR}/references/description-template.md`; it does **not** review the MR/PR — after opening, it hands off to the read-only/mutating review pair. ## What this does — and what it must not do Keep this boundary; it is why the skill is safe to compose. - **Does:** gather the diff / commits / ticket → author Background + High-Level Design (+ mermaid) + Pitfalls → draft the body to a file → open the MR/PR with it → suggest the review tail. - **Does NOT:** run `/etk:review-mr` or `/etk:post-mr-comments` for you, post inline comments, merge the MR/PR, or carry `/fix-bug`'s bug-only assumptions (a hardcoded target branch, a fixed bug label, file caps, an auto-appended `Fixes <ticket>` line). The review→post pair is a separate, human-gated boundary — never absorb or auto-run it. - **Never autonomous:** the drafted body must be human-approved before the MR/PR is created (the Step 3 gate); verify runs before authoring (Step 1) unless explicitly overridden. Never a single silent run. ## Flow ### Step 0 — Preflight Run `git rev-parse --abbrev-ref HEAD` for the branch and `git status --porcelain` for tree state. Confirm this is **not** a protected branch (main/master