How do I install the Create Pr skill?

Run npx skillmds@latest add tomevault-io/create-pr 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 Create Pr 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 Pr?

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

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

Who published Create Pr?

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

Create Pr by tomevault-io — Agent Skill

Name: Create Pr
Author: tomevault-io

Create Pr

Analyze changes, generate a well-structured PR, and create it via gh CLI. Use when user says "create PR", "open pull request", "submit PR", or after completing a feature branch. Includes summary, risk assessment, and test plan. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Create Pull Request

Create a high-quality Pull Request for the current branch.

Dynamic Context

Current branch: !git branch --show-current 2>/dev/null
Base branch: !echo "${ARGUMENTS:-$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo main)}"
Changed files: !git diff --name-status origin/main...HEAD 2>/dev/null || git diff --name-status origin/master...HEAD 2>/dev/null || echo "N/A"
Commit history: !git log --oneline origin/main...HEAD 2>/dev/null || git log --oneline origin/master...HEAD 2>/dev/null || echo "N/A"
Diff stats: !git diff --stat origin/main...HEAD 2>/dev/null || git diff --stat origin/master...HEAD 2>/dev/null || echo "N/A"

Process

1. Analyze Changes

Read all diffs and commit messages thoroughly
Categorize changes: feature / fix / refactor / docs / test / chore
Identify breaking changes and affected modules
Detect linked issues from commit messages or branch name

2. Generate PR Title

Conventional Commits format, under 72 characters:

feat: Add user authentication flow
fix: Resolve race condition in payment processing
refactor!: Extract shared validation logic (breaking)

3. Generate PR Body

## Summary

<!-- 1-3 bullet points describing WHY this change was made -->

## Changes

<!-- Grouped by category with file references -->

### Added

- `path/file.ts`: Description

### Modified

- `path/file.ts`: Description

## Breaking Changes

<!-- List any breaking changes with migration steps, or "None" -->

## Test Plan

- [ ] Unit tests added/updated
- [ ] Integration tests verified
- [ ] Manual testing steps documented

## Security Considerations

<!-- Any security implications, or "None identified" -->

## Related Issues

<!-- Closes #123, Fixes #456 -->

4. Create PR

Push current branch to remote if not already pushed
Run gh pr create with the generated title and body
Set labels based on change type (feature, bugfix, etc.)
Add reviewers if CODEOWNERS or team conventions exist

5. Post-Creation

Verify the PR URL is accessible
Report CI status if available
Display the PR link

Source: gr1m0h/dot — distributed by TomeVault.

---name: create-prdescription: Analyze changes, generate a well-structured PR, and create it via gh CLI. Use when user says "create PR", "open pull request", "submit PR", or after completing a feature branch. Includes summary, risk assessment, and test plan. Use when this capability is needed.---# Create Pull RequestCreate a high-quality Pull Request for the current branch.## Dynamic Context- Current branch: !`git branch --show-current 2>/dev/null`- Base branch: !`echo "${ARGUMENTS:-$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo main)}"`- Changed files: !`git diff --name-status origin/main...HEAD 2>/dev/null || git diff --name-status origin/master...HEAD 2>/dev/null || echo "N/A"`- Commit history: !`git log --oneline origin/main...HEAD 2>/dev/null || git log --oneline origin/master...HEAD 2>/dev/null || echo "N/A"`- Diff stats: !`git diff --stat origin/main...HEAD 2>/dev/null || git diff --stat origin/master...HEAD 2>/dev/null || echo "N/A"`## Process### 1. Analyze Changes- Read all diffs and commit messages thoroughly- Categorize changes: feature / fix / refactor / docs / test / chore- Identify breaking changes and affected modules- Detect linked issues from commit messages or branch name### 2. Generate PR TitleConventional Commits format, under 72 characters:- `feat: Add user authentication flow`- `fix: Resolve race condition in payment processing`- `refactor!: Extract shared validation logic` (breaking)### 3. Generate PR Body```markdown## Summary## Changes### Added- `path/file.ts`: Description### Modified- `path/file.ts`: Description## Breaking Changes## Test Plan- [ ] Unit tests added/updated- [ ] Integration tests verified- [ ] Manual testing steps documented## Security Considerations## Related Issues```### 4. Create PR- Push current branch to remote if not already pushed- Run `gh pr create` with the generated title and body- Set labels based on change type (feature, bugfix, etc.)- Add reviewers if CODEOWNERS or team conventions exist### 5. Post-Creation- Verify the PR URL is accessible- Report CI status if available- Display the PR link---> Source: [gr1m0h/dot](https://github.com/gr1m0h/dot) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions