skills.rest
g-zenr
g-zenrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr

Create pull requests for Git branches with pre-PR validation and structured titles.

Updated Feb 13, 2026
Search Tags:#automation#git#developer tools#code review#pull request#github
One-click install
npx skills add https://github.com/g-zenr/relay-api --skill pr-g-zenr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/g-zenr/relay-api/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/g-zenr/relay-api --skill pr-g-zenr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of pull requests, ensuring they meet project standards for titles, descriptions, and testing.

Core Features & Use Cases

  • Automated PR Generation: Creates pull requests with a standardized format.
  • Pre-PR Validation: Enforces passing tests and type checks before PR creation.
  • Change Analysis: Summarizes code changes for clear communication.
  • Use Case: After completing a feature on a new branch, use this Skill to automatically generate a well-formatted pull request ready for review.

Quick Start

Use the pr skill to create a pull request for the current branch.

Frequently Asked Questions about pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull request creation for a Git branch?▼

To automate pull request creation, this Skill generates a structured PR for your current Git branch, performing change analysis and creating standardized titles and bodies to streamline the workflow.

Can I enforce passing tests and type checks before a GitHub pull request is created?▼

Yes, you can enforce passing tests and type checks before a GitHub pull request is created using the built-in pre-PR validation, which ensures code quality standards are met prior to submission.

What is the best way to generate a standardized pull request body from code changes?▼

The best way to generate a standardized pull request body is using automated change analysis, which summarizes your code updates to ensure clear communication and consistent formatting for project reviewers.

Does this automated PR generation work with existing developer tools and CI workflows?▼

This automated PR generation integrates with your existing developer tools by validating branch changes and structuring the pull request output, fitting naturally into standard Git and code review workflows.

Why should I use an automated tool for GitHub pull requests instead of manual entry?▼

You should use an automated tool for GitHub pull requests to eliminate manual formatting errors, enforce project-specific documentation requirements, and consistently generate structured titles and bodies for efficient code reviews.

Related Skills

Explore More Software Engineering Skills→
aberrantCodeaberrantCode
1

ship-to-dev

Merge feature branches into DEV after passing tests and coverage gates.

Community
Advanced
cwijayasundaracwijayasundara
3

harness-core

Automate build, test, deployment, and code review in CI/CD pipelines.

Community
Advanced
otomattyotomatty
3

create-pull-request

Create and update GitHub pull requests with automated checks and template descriptions.

Community
Advanced
gqf2008gqf2008

github-pr-workflow

Automate GitHub pull request lifecycle from branch creation to merge.

Community
Advanced