How do I install the Pr Creator skill?

Run npx skillmds@latest add vybestack/pr-creator 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 Pr Creator 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 Pr Creator?

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 Pr Creator free to use?

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

Who published Pr Creator?

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

Pr Creator by vybestack — Agent Skill

Name: Pr Creator
Author: vybestack

File contents

Pull Request Creator

This skill guides the creation of high-quality Pull Requests that adhere to the repository's standards.

Workflow

Follow these steps to create a Pull Request:

Locate Template: Search for a pull request template in the repository.
- Check .github/pull_request_template.md
- Check .github/PULL_REQUEST_TEMPLATE.md
- If multiple templates exist (e.g., in .github/PULL_REQUEST_TEMPLATE/), select the most appropriate one based on the context (e.g., bug_fix.md vs feature.md).
Read Template: Read the content of the identified template file.
Draft Description: Create a PR description that strictly follows the template's structure.
- Headings: Keep all headings from the template.
- Checklists: Review each item. Mark with [x] if completed. If an item is not applicable, leave it unchecked or mark as [ ] (depending on the template's instructions) or remove it if the template allows flexibility (but prefer keeping it unchecked for transparency).
- Content: Fill in the sections with clear, concise summaries of your changes.
- Related Issues: Link any issues fixed or related to this PR (e.g., "Fixes #123").
Create PR: Use the gh CLI to create the PR.
```
gh pr create --title "type(scope): succinct description" --body "..."
```
- Title: Ensure the title follows the Conventional Commits format if the repository uses it (e.g., feat(ui): add new button, fix(core): resolve crash).
** DO NOT CHANGE THE PR DESCRIPTION TO THE LAST THING YOU DID WHEN YOU MAKE CHANGES ** You can amend the PR if the changes you make materially change its behavior but do not change the whole description to just match your last commit. the PR description should be holistic. This is an LLM bad habit that makes it hard to review PRs.

Principles

Compliance: Never ignore the PR template. It exists for a reason.
Completeness: Fill out all relevant sections.
Accuracy: Don't check boxes for tasks you haven't done.

---name: pr-creatordescription: Use this skill when asked to create a pull request (PR). It ensures all PRs follow the repository's established templates and standards.---# Pull Request CreatorThis skill guides the creation of high-quality Pull Requests that adhere to the repository's standards.## WorkflowFollow these steps to create a Pull Request:1. **Locate Template**: Search for a pull request template in the repository. - Check `.github/pull_request_template.md` - Check `.github/PULL_REQUEST_TEMPLATE.md` - If multiple templates exist (e.g., in `.github/PULL_REQUEST_TEMPLATE/`), select the most appropriate one based on the context (e.g., `bug_fix.md` vs `feature.md`).2. **Read Template**: Read the content of the identified template file.3. **Draft Description**: Create a PR description that strictly follows the template's structure. - **Headings**: Keep all headings from the template. - **Checklists**: Review each item. Mark with `[x]` if completed. If an item is not applicable, leave it unchecked or mark as `[ ]` (depending on the template's instructions) or remove it if the template allows flexibility (but prefer keeping it unchecked for transparency). - **Content**: Fill in the sections with clear, concise summaries of your changes. - **Related Issues**: Link any issues fixed or related to this PR (e.g., "Fixes #123").4. **Create PR**: Use the `gh` CLI to create the PR. ```bash gh pr create --title "type(scope): succinct description" --body "..." ``` - **Title**: Ensure the title follows the [Conventional Commits](https://www.conventionalcommits.org/) format if the repository uses it (e.g., `feat(ui): add new button`, `fix(core): resolve crash`).5. ** DO NOT CHANGE THE PR DESCRIPTION TO THE LAST THING YOU DID WHEN YOU MAKE CHANGES ** You can amend the PR if the changes you make materially change its behavior but do not change the whole description to just match your last commit. the PR description should be holistic. This is an LLM bad habit that makes it hard to review PRs.## Principles- **Compliance**: Never ignore the PR template. It exists for a reason.- **Completeness**: Fill out all relevant sections.- **Accuracy**: Don't check boxes for tasks you haven't done.

Frequently asked questions

Pr Creator