agentsclimarketplace
Sign in

Create pull request

Skill helderberto/agent-skills/skills/create-pull-request

Create a GitHub pull request — fills the repo's PR template, conventional-commit title, ticket refs. Draft mode via `--draft`.From its SKILL.md

Install
npx -y skills add helderberto/agent-skills --skill create-pull-request

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

2 things to look at

  • 12 stars12 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.
  • runs commandsInstructs the agent to run 5 commands, including `git fetch origin && git remote show origin | grep 'HEAD branch' | cut -d' ' -f5` and 4 more.

SKILL.md

2.6 KB, 632 tokens by cl100k_base, as published. Nobody here has run it

Create Pull Request

Mode: $ARGUMENTS

If --draft is passed, create as draft PR.

Workflow

  1. Run in parallel:
    • git fetch origin && git remote show origin | grep 'HEAD branch' | cut -d' ' -f5 (get base branch)
    • git rev-parse --abbrev-ref HEAD | grep -oE '[A-Z]+-[0-9]+' (extract ticket ID)
    • Search for PR template in order: .github/pull_request_template.md, .github/PULL_REQUEST_TEMPLATE.md, .github/PULL_REQUEST_TEMPLATE/ (directory of templates), docs/pull_request_template.md, pull_request_template.md
  2. Run in parallel:
    • git diff HEAD
    • git diff [base-branch]...HEAD --unified=0
  3. If a PR template was found, read it in full — it becomes the canonical structure for the PR body. Do not paraphrase or skip sections.
  4. Review ALL commits (not just latest)
  5. Ask the user (use AskUserQuestion when available; otherwise ask directly). Ask all at once where possible:
    • Effort (required): how long the task took in hours (planning, reading, testing, all included)
    • Changes (required): general overview of what was done
    • Testing (optional): testing done that isn't visible in the diff
    • Tricky parts (optional): anything hard, requiring multiple attempts, or non-obvious
    • If template found, also surface any template-specific fields that can't be inferred from the diff (e.g. "Does this include breaking changes?", "What type of change is this?")
  6. Draft title and body:
    • Title must match: /^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test)(\(.*\))?: .+$/
    • If template found: use the template verbatim as the body base — fill every section/placeholder using diff + user answers; check applicable checkboxes; do NOT add sections not in the template; do NOT omit any template sections
    • If no template: use Summary + Test plan
    • Reference ticket ID in body if found (e.g. Resolves TICKET-123)
    • Incorporate user's answers into description — don't just repeat the diff
  7. In parallel:
    • Create branch if needed
    • Push with -u if needed
    • Create PR with gh pr create using HEREDOC (add --draft if requested)

Rules

  • If a PR template exists, the body MUST be the filled template — not a summary that references it
  • Return PR URL when done
  • Use gh CLI only
  • NEVER force push to main/master
  • NEVER push without user confirmation if already on main/master
  • NEVER create PR with uncommitted changes — commit first

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

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

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

  • Review all commits
  • Ask user for effort and changes
  • Fill template sections verbatim
  • Reference ticket ID in body

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. 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.