How do I install the Git Pr skill?

Run npx skillmds@latest add tomevault-io/git-pr-4 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 Git Pr 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 Git 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 Git Pr free to use?

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

Who published Git Pr?

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

Git Pr by tomevault-io — Agent Skill

Name: Git Pr
Author: tomevault-io

File contents

Git PR

Prepares comprehensive PR content for manual creation. I prefer to open PRs manually because it's the moment I review and ensure everything is correct.

Usage

/git-pr [target-branch]

Default target: main

Why Manual PR Creation?

Opening PRs manually allows me to:

Review all changes one final time before submitting
Verify the PR title and description are accurate
Check that only intended changes are included
Ensure quality before sharing with the team

Workflow

Analyze branch:

scripts/pr-helper.sh analyze [target-branch]

Generate PR content:
```
scripts/pr-helper.sh generate [target-branch]
```
Creates complete PR description in the format below
Review output:
- Read the generated title and description
- Verify all sections are accurate
Open PR manually:
- Go to GitHub/GitLab web interface
- Use the generated title and description
- Submit the PR

PR Format

Title

<type>: Brief description

Examples:

feat: add user authentication
fix: resolve memory leak in parser
docs: update installation guide

Description Template

## Summary
Brief overview of what this PR accomplishes.

## What, Why & Benefits

**What:**
- Change 1
- Change 2

**Why:**
Explanation of the motivation behind these changes

**Benefits:**
- Benefit 1
- Benefit 2

## Validation
- [ ] Code follows project conventions
- [ ] Self-review completed
- [ ] No sensitive data in changes
- [ ] Tests pass locally

## Changes
| File | Change |
|------|--------|
| `path/to/file1` | Brief description |
| `path/to/file2` | Brief description |

## Testing/Validations
- [ ] Tested locally
- [ ] Unit tests added/updated
- [ ] Integration tests pass
- [ ] Manual testing completed

Scripts

scripts/pr-helper.sh analyze [target] - Analyze branch changes
scripts/pr-helper.sh generate [target] - Generate complete PR content
scripts/pr-helper.sh summary [target] - Show branch summary

Best Practices

Always review generated content before using
Ensure description accurately reflects changes
Include context for reviewers
Check all validation checkboxes

Safety

Never include sensitive data in PR descriptions
Verify branch is clean before generating
Double-check target branch is correct

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

---name: git-pr-4description: Prepare comprehensive PR content for manual creation. Use when analyzing branch changes, generating PR descriptions, or preparing to open a pull request. Use when this capability is needed.---# Git PRPrepares comprehensive PR content for manual creation. I prefer to open PRs manually because it's the moment I review and ensure everything is correct.## Usage```/git-pr [target-branch]```Default target: `main`## Why Manual PR Creation?Opening PRs manually allows me to:- Review all changes one final time before submitting- Verify the PR title and description are accurate- Check that only intended changes are included- Ensure quality before sharing with the team## Workflow1. **Analyze branch**: ```bash scripts/pr-helper.sh analyze [target-branch] ```2. **Generate PR content**: ```bash scripts/pr-helper.sh generate [target-branch] ``` Creates complete PR description in the format below3. **Review output**: - Read the generated title and description - Verify all sections are accurate4. **Open PR manually**: - Go to GitHub/GitLab web interface - Use the generated title and description - Submit the PR## PR Format### Title```<type>: Brief description```Examples:- `feat: add user authentication`- `fix: resolve memory leak in parser`- `docs: update installation guide`### Description Template```markdown## SummaryBrief overview of what this PR accomplishes.## What, Why & Benefits**What:**- Change 1- Change 2**Why:**Explanation of the motivation behind these changes**Benefits:**- Benefit 1- Benefit 2## Validation- [ ] Code follows project conventions- [ ] Self-review completed- [ ] No sensitive data in changes- [ ] Tests pass locally## Changes| File | Change ||------|--------|| `path/to/file1` | Brief description || `path/to/file2` | Brief description |## Testing/Validations- [ ] Tested locally- [ ] Unit tests added/updated- [ ] Integration tests pass- [ ] Manual testing completed```## Scripts- `scripts/pr-helper.sh analyze [target]` - Analyze branch changes- `scripts/pr-helper.sh generate [target]` - Generate complete PR content- `scripts/pr-helper.sh summary [target]` - Show branch summary## Best Practices- Always review generated content before using- Ensure description accurately reflects changes- Include context for reviewers- Check all validation checkboxes## Safety- Never include sensitive data in PR descriptions- Verify branch is clean before generating- Double-check target branch is correct---> Converted and distributed by [TomeVault](https://tomevault.io/claim/mateusoliveirab) — claim your Tome and manage your conversions.

Frequently asked questions

Git Pr