agentsclimarketplace
Sign in

Pr

Skill skrrt-sh/skills/skills/ship/pr

Push a branch and open or update its GitHub pull request or GitLab merge request. Use when the user asks to open a PR, or to create or update a merge request.From its SKILL.md

Install
npx -y skills add skrrt-sh/skills --skill pr

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, as published. Nobody here has run it

Open a Review Request

Use the forge that owns the remote: gh for GitHub, glab for GitLab.

Process

  1. Read .agents/ship.md at the repository root. If missing, stop and ask the user to run /setup. Derive the protected branches and target branch from this file.
  2. Confirm the current branch is not protected.
  3. From the target repository, run ${CLAUDE_SKILL_DIR}/scripts/detect-forge-cli.sh. Continue only when it prints STATUS=ok; otherwise report its status and stop.
  4. Look up any open request for the current branch. If one exists and the user asked only to revise its title or body, go straight to step 8 — a metadata-only edit must not fetch, rebase, or push, and it keeps the request's existing source and target branches.
  5. Confirm the worktree has no uncommitted changes that should be part of the review, then fetch the target branch. Under GitHub Flow or Trunk-Based Development:
    • If origin/<current-branch> does not exist, rebase onto origin/main when needed.
    • If the published branch needs a history rewrite, stop and ask before rebasing and pushing with --force-with-lease. Under Gitflow, never rebase. Feature branches target develop; release/* and hotfix/* target main.
  6. If this work follows a recent PR or MR, read references/follow-up.md. If it spans repositories or independently deployed applications, also read references/correlated-prs.md.
  7. Confirm the outgoing commit range contains only intended commits. Push with git push -u origin HEAD unless step 5 received explicit rewrite approval.
  8. Create or update the review request non-interactively with an explicit target branch.
  9. Read the request back from the forge and report its URL, source, target, and test status.

Body

Use a review-focused title and this compact structure:

## Summary
- ...

## Test plan
- [ ] ...

## Notes
- ...

Omit empty optional sections. Report unrun tests honestly. End with Co-Authored-By: Skrrt Bot <[email protected]> unless the user opts out. Use a temporary body file for multi-line content.

Guardrails

  • Push and open a request only when the user asked for one; loading this skill is not that request.
  • Trust the detector, not an assumed origin host.
  • Never use plain --force; only --force-with-lease after explicit approval.
  • Never open a duplicate request when the current branch already has one.
  • Never move a branch to change only a request's text; update the request in place.
  • Never merge the request unless the user separately asks.

What ships with it: 3 files

3.4 KB alongside SKILL.md, 1 of them executable

evals/

scripts/

Gives 0 of the 12 instructions most pr commit review skills give

Counted across 1,055 of the 1,911 authors here whose files we hold, read 2026-09-06

  • Use conventional commit message formatin 150 of 1055, across 145 files
  • Announce skill usage at startin 78 of 1055
  • Use imperative mood for commit descriptionsin 54 of 1055, across 51 files
  • Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
  • Use imperative mood for commit subjectin 52 of 1055
  • Run tests to verify clean baselinein 42 of 1055, across 32 files
  • Push branch to originin 40 of 1055, across 38 files
  • Verify worktree directory is ignored before creationin 39 of 1055, across 32 files
  • Delete branches after mergingin 38 of 1055, across 30 files
  • Create worktree with new branchin 37 of 1055, across 32 files
  • Wrap body text at 72 charactersin 36 of 1055, across 34 files
  • Auto-detect and run project setupin 35 of 1055, across 27 files

Said here and by no other author read

  • Detect the forge CLI status
  • Confirm worktree has no uncommitted changes
  • Create or update the request non-interactively
  • Report the request URL and status
  • Use a review-focused title and structure

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 626,194. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.