How do I install the Create Pull Request skill?

Run npx skillmds@latest add tomevault-io/create-pull-request-2 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.

What does the Create Pull Request skill do?

Steps for creating a pull request in this project. Use when this capability is needed. It is listed under Coding & Dev Tools on SkillMD.

Is Create Pull Request safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Create 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 Create Pull Request free to use?

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

Who published Create Pull Request?

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

Create Pull Request by tomevault-io

Name: Create Pull Request
Author: tomevault-io

File contents

Requirements

GitHub CLI (gh) installed and authenticated
- gh pr create — open the PR creation flow.
- gh pr view — verify the PR was created correctly.
On a feature branch (not main)

Steps

Infer from context or ask the user if this PR fixes or relates to an issue, follow up and ask for the issue number before proceeding.
Infer from context or ask the user to describe their AI involvement and review state:
- AI generated the code and PR description — has it been reviewed by a human?
- AI assisted with the PR description only — has it been reviewed by a human?
- Other (ask user to describe) — has it been reviewed by a human?
Verify any needed docs and tests changes have been included.
Run appropriate quality assurance locally before opening the PR.

PR title guidance

Use a descriptive title that communicates the problem solved or feature added in a few words.
Do not use vague titles like "Fixes #123" — write "Fix documentation dark mode refresh issue (#123)" instead.

Template

If fully closes: Fixes #number | If related: Relates to #number Fixes/Relates to #

Description

Describe the "why" of the changes. Concisely, why the proposed solution is the right one, and which other solutions might have been skipped.
Highlight areas of the proposed changes that require careful review.
Guidance on QA done so far vs. testing left to do.

Testing

Summarise results briefly, e.g. "All tests pass, no lint errors"
Only report lint/test results for files included in this PR. Do not mention unrelated or untracked files.
Share guidance on any specific tests related to the PR - command(s) and results.
For frontend changes, add before/after screenshots if possible.
Note any testing still left to do or areas needing careful review

AI usage

Agent: infer from your context / share user input.

Source: wagtail/guide — distributed by TomeVault.

---name: create-pull-request-2description: Steps for creating a pull request in this project. Use when this capability is needed.---## Requirements- GitHub CLI (`gh`) installed and authenticated - `gh pr create` — open the PR creation flow. - `gh pr view` — verify the PR was created correctly.- On a feature branch (not main)## Steps- Infer from context or ask the user if this PR fixes or relates to an issue, follow up and ask for the issue number before proceeding.- Infer from context or ask the user to describe their AI involvement and review state: - AI generated the code and PR description — has it been reviewed by a human? - AI assisted with the PR description only — has it been reviewed by a human? - Other (ask user to describe) — has it been reviewed by a human?- Verify any needed docs and tests changes have been included.- Run appropriate quality assurance locally before opening the PR.## PR title guidance- Use a descriptive title that communicates the problem solved or feature added in a few words.- Do not use vague titles like "Fixes #123" — write "Fix documentation dark mode refresh issue (#123)" instead.## Template- If fully closes: Fixes #number | If related: Relates to #number Fixes/Relates to #### Description- Describe the "why" of the changes. Concisely, why the proposed solution is the right one, and which other solutions might have been skipped.- Highlight areas of the proposed changes that require careful review.- Guidance on QA done so far vs. testing left to do.### Testing- Summarise results briefly, e.g. "All tests pass, no lint errors"- Only report lint/test results for files included in this PR. Do not mention unrelated or untracked files.- Share guidance on any specific tests related to the PR - command(s) and results.- For frontend changes, add before/after screenshots if possible.- Note any testing still left to do or areas needing careful review### AI usage- Agent: infer from your context / share user input.---> Source: [wagtail/guide](https://github.com/wagtail/guide) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Create Pull Request