pr

Plugin pr from marketplace cjus-skills in cjus/cjus-skills. Commands read from the repo's manifest — 12 days ago.

Skills (22)

• abort

  Abandon a branch that will never merge. Closes its issue as not planned, closes any open PR, removes the worktree, and deletes the branch locally and on the remote. Permanent, so it only runs when the user invokes it explicitly. Use when the user says "/pr:abort <reason>".

• cleanup

  Tear down a merged branch's workspace by ticket number. Verifies the close ran and the PR actually merged, confirms the issue closed, removes the worktree, deletes the branch, and pulls the merge. Destructive, so it only runs when the user invokes it explicitly.

• close

  Close a branch so it can merge. Runs the summary, conflict, migration-drift and check gates, a review gate, links the GitHub issue with a verified closing reference, writes the handoff artifacts, triages deferred work, then commits and pushes. Required before any merge. Use when the user says "/pr:c

• commitmsg

  Write COMMITMSG.md in the branch's plan folder, covering only the uncommitted changes. Use when the user says "/pr:commitmsg", asks for a commit message, or when /pr:close needs the message its commit will use.

• condense

  Refresh PLAN.md status and shrink an oversized CHANGELOG.md for the current branch, preserving timestamps. Use when the user says "/pr:condense", when the branch's changelog has grown unwieldy, or as a step of /pr:close.

• continuity-add

  Write one concise continuity entry as a new file under the repo-root continuity folder, sourced from the branch's plan folder, its commits and its PR. Additive only, touching no existing entry. Use when the user says "/pr:continuity-add", or as the handoff step of /pr:close.

• continuity-prune

  Delete continuity entry files older than a cutoff date, after showing the list and asking. Destructive, so it only runs when the user invokes it explicitly. Use when the user says "/pr:continuity-prune <YYYY-MM-DD>".

• cp

  Stage everything, commit with a concise message, and push the current branch. Use when the user says "/pr:cp" or asks to commit and push.

• init

  Set a repo up for the pr plugin. Detects the GitHub repo, the package manager and the check commands, asks about the choices it cannot detect, writes .claude/pr-config.json, creates the status and priority labels the queue runs on, and checks that squash merges take the PR title. Use when the user s

• next

  Recommend which ticket to work on next by cross-referencing recent PR activity and local worktrees against the open status:todo queue, high priority then medium. Each candidate comes with its derived branch name. Use when the user says "/pr:next" or asks what to work on next.

• plan-check

  Check whether the branch's PLAN.md still matches reality, refresh its status, and state the concrete next steps. Use when the user says "/pr:plan-check", asks whether the plan is current, or wants to know what is left on the branch.

• pre-test

  Review the branch and decide whether it is ready for hands-on testing. Refreshes PLAN.md status, opens a draft PR so CI starts running, runs the configured checks, and runs a code review. Use when the user says "/pr:pre-test", asks whether the branch is ready to test, or wants a review pass before c

• precompact

  Bring PLAN.md fully current before a context compaction, including explicit resume steps written for an agent with none of the current context. Use when the user says "/pr:precompact" or right before a compaction.

• resume

  Establish the actual current state of a branch after a break, from git, GitHub and the branch's own documents rather than from conversation memory, and lead with the open questions and blockers. Use when the user says "/pr:resume" or returns to work after time away.

• reviews

  Summarize what was recently completed, from the continuity entries, the assertions file and merged PRs, then cross-reference the open status:todo queue to recommend what to work on next. Use when the user says "/pr:reviews" or asks "what did we just do and what is next".

• sanity

  Re-audit the factual claims in your immediately previous response, classifying each as verified, inferred or unsupported, and issue corrections for anything that does not hold. Use when the user says "/pr:sanity" or asks you to double-check what you just asserted.

• start

  Begin work on a ticket. Creates the branch (in a worktree when configured), installs dependencies, initializes the branch's plan folder, enriches PLAN.md from the GitHub issue, and moves the issue to status:in-progress. Use when the user says "/pr:start <branch-name>" or asks to start work on a tick

• status

  Explain in plain language what the current branch does and what it now prevents, plus where it sits in the lifecycle. A 20-second read that writes nothing. Use when the user says "/pr:status" or asks for a quick rundown of what has been done on this branch.

• summary

  Write a comprehensive summary of the completed work on this branch into the plan folder, with code examples, plan alignment, testing notes and an impact assessment. Use when the user says "/pr:summary", asks for a PR write-up, or when /pr:close needs the document that becomes the PR body.

• sync

  Assess what the default branch's new commits mean for every live worktree, then merge them into the current one. Stays silent when nothing intersects. Use when the user says "/pr:sync", after a PR merges, or when the default branch has moved and you need to know which branches are affected.

• ticket

  Create a GitHub issue from a freeform description, labelled status:todo with priority:high, and report the branch name it yields. Use when the user says "/pr:ticket <description>", asks to file or open a ticket, or when /pr:close triages deferred work into a follow-up issue.

• triage

  Review every open GitHub issue against the state of the default branch, closing the ones the work has already retired, stamping the ones that still hold with a last-reviewed record, and consolidating issues that have converged on one piece of work. Reports only by default; writes with --apply. Use w

Subagents (1)

• code-reviewer

  Review the changes on the current branch for bugs, edge cases and convention violations, with mentorship-style feedback and a machine-parseable verdict. Detects the branch context and reviews the whole PR diff. Invoked by /pr:pre-test and by /pr:close's review gate, or directly when the user asks fo

Hooks (3)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/on-session-start.sh"

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/guard-default-branch.sh"

• Stop

  "${CLAUDE_PLUGIN_ROOT}/hooks/verify-close-landed.sh"

Similar plugins