← ClaudeAtlas

cm-prlisted

Open a GitHub pull request for the current branch following `.github/pull_request_template.md`. Use whenever the user says "open a PR", "create a PR", "let's PR this", "ship it", "raise a PR", invokes `/cm-pr`, OR when, after finishing an implementation task, you (the agent) decide a PR is the right next step. Drafts title + body, fills every template section including a reviewer-facing **How to validate** block, and shows the exact `gh pr create` command. NEVER pushes, opens, edits, or merges a PR without an explicit `go` from the user in the current turn — propose, then wait.
pigorv/claude-monitor · ★ 10 · Code & Development · score 73
Install: claude install-skill pigorv/claude-monitor
# cm-pr (claude-monitor) You open pull requests against `pigorv/claude-monitor` (or whatever remote the working tree points at). Your job is to turn the current branch into a clean, reviewable PR — a tight title, a body that fills every section of `.github/pull_request_template.md`, and a **How to validate** block a reviewer can actually act on. You never push or call `gh pr create` until the user replies `go` (or equivalent) in the current turn. ## When to invoke this skill Trigger this skill — without being asked again — whenever any of the following is true: - The user says "open/create/raise a PR", "let's PR this", "ship it", "PR up", or types `/cm-pr`. - You (the agent) just finished an implementation task on a feature branch and a PR is the natural next step. Do **not** silently skip the proposal-and-approval gate just because the user implied "and PR it" earlier — always show the draft and wait for `go`. - The user asks to "update the PR" — in that case run the same workflow but use `gh pr edit` in the apply step instead of `gh pr create` (only if a PR for this branch already exists; check first with `gh pr view --json url,number`). Do **not** invoke this skill when: - There are no commits ahead of the base branch (nothing to PR). - The user wants a draft commit message only (use the regular commit flow, not this skill). - The user wants a code review of the diff before opening — run `cm-review` first, then this skill. ## Inputs (`$ARGUMENTS`) | Token | Effect