# Sending Pull Request

> Prepare a conventional branch, write or review a pull/merge request title and body, then push and create or update the GitHub PR. Use when work is ready for review or PR/MR copy needs drafting or review.

- Skill: `wkentaro/sending-pull-request` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add wkentaro/sending-pull-request`
- Raw SKILL.md: https://api.skillmd.com/api/skills/wkentaro/sending-pull-request/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: wkentaro (https://skillmd.com/u/wkentaro)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/wkentaro/sending-pull-request

---


# Send a pull request

When asked only to write or review a PR/MR title or body, inspect the supplied context, read [BODY.md](BODY.md), and return the copy without changing the repository or forge. If evidence is requested, read [MEDIA.md](MEDIA.md) for formatting guidance, use supplied evidence only, and mark unverified evidence as pending. Do not run capture or publishing workflows for a copy-only request.

To send work for review:

1. Fetch `origin`, resolve the current and default branches, and inspect commits and working-tree changes against `origin/<default>`. Stop if there is no work to send.

2. Put the work on a conventional `<type>/<short-kebab-description>` branch without stashing or changing it:

   - Keep a conventional non-default branch.
   - On the default branch, choose the name from the work using its Conventional Commit type, then preserve every commit and working-tree change before resetting the local default branch:

     ```bash
     git switch --no-track -c <new-branch>
     git branch -f <default> origin/<default>
     ```

   - Rename a clearly auto-generated placeholder branch with `git branch -m <new-branch>`.
   - Stop on another non-conventional branch unless the user asked to rename it.

3. Verify that the branch and work are unchanged. Stop if any intended change is uncommitted.

4. Inspect the commits and diff against the default branch. Write a Conventional Commit title under 70 characters, read [BODY.md](BODY.md), and write the body from what the diff cannot explain. Preserve any existing `<!-- before-and-after:start/end -->` block until the evidence assessment below.

5. Check for an open PR from the current branch. Push with tracking; use `--force-with-lease` only after an intentional history rewrite.

6. Create a draft PR with `--assignee @me`, or update the existing PR's title and body, using a temporary `--body-file` and deleting it afterward. Keep an existing PR in draft while evidence is pending, using `gh pr ready --undo` if needed.

7. Assess evidence on every PR creation or update, including nonvisual changes, following [MEDIA.md](MEDIA.md). This skill owns the evidence decision, text evidence, verification, and recovery. Invoke the existing `before-and-after` skill for screenshots or recordings that need capturing or publishing; it needs no modifications or new result contract.

8. On verified evidence or an intentional skip, apply the intended readiness: a direct user invocation makes the PR ready with `gh pr ready`; an autonomous invocation leaves a draft unless the user requested otherwise. On failure, leave the PR as a draft and report the missing evidence or blocker with the PR URL. Never merge or approve the PR.