How do I install the Pull Request skill?

Run npx skillmds@latest add caldiaworks/pull-request in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pull Request safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pull Request?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pull Request free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pull Request?

caldiaworks (@caldiaworks) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pull Request by caldiaworks — Agent Skill

Name: Pull Request
Author: caldiaworks

Pull Request

Create GitHub pull requests with readiness checks, auto-drafted titles and descriptions, and remote push handling. Use when: create PR, pull request, open PR, submit PR, create pull request, PR for review, push and PR, pull-request, /pull-request.

caldiaworks 6b89a0d 2.4 KB Updated Sep 17, 2026

File contents

Pull Request Creation

Create a GitHub pull request for the current branch. Works in any Git repository with GitHub as the remote.

Pull requests are created at the user's discretion -- this skill is never triggered automatically after commits.

Workflow

Step 1: Readiness Check

Verify the branch is ready for a pull request.

Check that the current branch has commits ahead of the base branch using git log <base>..HEAD.
If there are no commits ahead, inform the user there is nothing to create a PR for and stop.
If the current branch is not pushed to the remote, push it with tracking: git push -u origin <branch>.
Check if a PR already exists for the current branch using gh pr view. If one exists, display the existing PR URL and ask the user whether to update it or abort.

Step 2: Draft and Create PR

Generate a title and body from the commit history, then create the PR.

Display the commit log between the base branch and HEAD: git log --oneline <base>..HEAD.
Display the full diff: git diff <base>...HEAD.
Draft a PR title (under 72 characters) and body:
- Title: concise summary of the changes in imperative form
- Body: structured summary with sections as appropriate
- Follow repository conventions if visible from recent PRs

Create the pull request:

gh pr create --title "<title>" --body "$(cat <<'EOF'
<body>
EOF
)"

Display the PR number and URL.

Error Handling

If PR creation fails, display the error message returned by gh pr create.

Before Finishing

After creating the PR, review it from a reviewer's perspective:

Understandable? Can a reviewer who has no context about the conversation understand what this PR does and why, from the title and body alone?
Complete? Does the diff include all intended changes? Check git status for unstaged changes that may have been missed.

Constraints

Do not merge the PR -- creation only.
Do not force-push or rebase without explicit user request.
The base branch defaults to the repository's default branch unless the user specifies otherwise.

---name: pull-requestdescription: Create GitHub pull requests with readiness checks, auto-drafted titles and descriptions, and remote push handling. Use when: create PR, pull request, open PR, submit PR, create pull request, PR for review, push and PR, pull-request, /pull-request.---# Pull Request CreationCreate a GitHub pull request for the current branch. Works in any Git repository with GitHub as the remote.Pull requests are created at the user's discretion -- this skill is never triggered automatically after commits.## Workflow### Step 1: Readiness CheckVerify the branch is ready for a pull request.1. Check that the current branch has commits ahead of the base branch using `git log <base>..HEAD`.2. If there are no commits ahead, inform the user there is nothing to create a PR for and stop.3. If the current branch is not pushed to the remote, push it with tracking: `git push -u origin <branch>`.4. Check if a PR already exists for the current branch using `gh pr view`. If one exists, display the existing PR URL and ask the user whether to update it or abort.### Step 2: Draft and Create PRGenerate a title and body from the commit history, then create the PR.1. Display the commit log between the base branch and HEAD: `git log --oneline <base>..HEAD`.2. Display the full diff: `git diff <base>...HEAD`.3. Draft a PR title (under 72 characters) and body: - Title: concise summary of the changes in imperative form - Body: structured summary with sections as appropriate - Follow repository conventions if visible from recent PRs4. Create the pull request: ```bash gh pr create --title "<title>" --body "$(cat <<'EOF' <body> EOF )" ```5. Display the PR number and URL.### Error HandlingIf PR creation fails, display the error message returned by `gh pr create`.## Before FinishingAfter creating the PR, review it from a reviewer's perspective:- **Understandable?** Can a reviewer who has no context about the conversation understand what this PR does and why, from the title and body alone?- **Complete?** Does the diff include all intended changes? Check `git status` for unstaged changes that may have been missed.## Constraints- Do not merge the PR -- creation only.- Do not force-push or rebase without explicit user request.- The base branch defaults to the repository's default branch unless the user specifies otherwise.

Frequently asked questions