How do I install the Create Pr skill?

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

File contents

Create Pull Request Skill

Create GitHub pull requests by analyzing branch diff and following the project template.

Prerequisites

On a feature branch (not main)
Changes committed locally
GitHub CLI (gh) authenticated

Workflow

1. Gather Context

# Get current branch name
git branch --show-current

# Check if branch is pushed
git status

# Get diff against main
git diff main...HEAD --stat
git diff main...HEAD

# Get commit history for this branch
git log main..HEAD --oneline

2. Analyze Changes

Review the diff to understand:

What: Files changed, functions modified, features added/removed
Why: The purpose behind the changes (bug fix, feature, refactor)
Testing: What tests were added or should be run

3. Create PR

Use gh pr create with the project template structure:

gh pr create --title "<type>: <description>" --body "$(cat <<'EOF'
Fixes #issue-number-here

# What

- [Describe specific changes made]
- [List modified components/files]

# Why

- [Explain the motivation]
- [Reference related issues]

# Testing done

- [List tests run]
- [Describe manual testing]

# Decisions made

- [Document any non-obvious choices]

# Checks

- [x] I have tested this code
- [x] I have reviewed my own PR
- [ ] I have created an issue for this PR
- [x] I have set a descriptive PR title compliant with conventional commits

# Reviewing tips

- [Guidance for reviewers]

# User facing release notes

- [Changes visible to end users, if any]
EOF
)"

Conventional Commit Types

Type	Use Case
feat	New feature
fix	Bug fix
docs	Documentation only
style	Formatting, no code change
refactor	Code change, no feature/fix
perf	Performance improvement
test	Adding/fixing tests
chore	Maintenance, deps, config

Examples

Feature PR

gh pr create --title "feat: add user authentication" --body "..."

Bug Fix PR

gh pr create --title "fix: resolve timeout in consensus worker" --body "..."

With Issue Link

gh pr create --title "fix: handle empty contract data" --body "Fixes #123..."

Tips

Keep PR title under 72 characters
Reference issue numbers with Fixes #N or Closes #N for auto-close
For WIP, use gh pr create --draft
Push branch first if needed: git push -u origin $(git branch --show-current)

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: create-pr-27description: Create GitHub pull requests by analyzing branch diff and following the project template Use when this capability is needed.---# Create Pull Request SkillCreate GitHub pull requests by analyzing branch diff and following the project template.## Prerequisites- On a feature branch (not main)- Changes committed locally- GitHub CLI (`gh`) authenticated## Workflow### 1. Gather Context```bash# Get current branch namegit branch --show-current# Check if branch is pushedgit status# Get diff against maingit diff main...HEAD --statgit diff main...HEAD# Get commit history for this branchgit log main..HEAD --oneline```### 2. Analyze ChangesReview the diff to understand:- **What**: Files changed, functions modified, features added/removed- **Why**: The purpose behind the changes (bug fix, feature, refactor)- **Testing**: What tests were added or should be run### 3. Create PRUse `gh pr create` with the project template structure:```bashgh pr create --title "<type>: <description>" --body "$(cat <<'EOF'Fixes #issue-number-here# What- [Describe specific changes made]- [List modified components/files]# Why- [Explain the motivation]- [Reference related issues]# Testing done- [List tests run]- [Describe manual testing]# Decisions made- [Document any non-obvious choices]# Checks- [x] I have tested this code- [x] I have reviewed my own PR- [ ] I have created an issue for this PR- [x] I have set a descriptive PR title compliant with conventional commits# Reviewing tips- [Guidance for reviewers]# User facing release notes- [Changes visible to end users, if any]EOF)"```## Conventional Commit Types| Type | Use Case ||------|----------|| feat | New feature || fix | Bug fix || docs | Documentation only || style | Formatting, no code change || refactor | Code change, no feature/fix || perf | Performance improvement || test | Adding/fixing tests || chore | Maintenance, deps, config |## Examples### Feature PR```bashgh pr create --title "feat: add user authentication" --body "..."```### Bug Fix PR```bashgh pr create --title "fix: resolve timeout in consensus worker" --body "..."```### With Issue Link```bashgh pr create --title "fix: handle empty contract data" --body "Fixes #123..."```## Tips- Keep PR title under 72 characters- Reference issue numbers with `Fixes #N` or `Closes #N` for auto-close- For WIP, use `gh pr create --draft`- Push branch first if needed: `git push -u origin $(git branch --show-current)`---> Converted and distributed by [TomeVault](https://tomevault.io/claim/genlayerlabs) — claim your Tome and manage your conversions.

Frequently asked questions

Create Pr