skills.rest
pegasus-isi
pegasus-isiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pr

Create GitHub pull requests after validating CI status and branch integrity.

Updated Feb 13, 2026
Search Tags:#automation#git#workflow#pull request#github#ci
One-click install
npx skills add https://github.com/pegasus-isi/claude-plugin-marketplace --skill pr-pegasus-isi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/pegasus-isi/claude-plugin-marketplace/tree/main/plugins/pegasus-dev/skills/pr
Command: npx skills add https://github.com/pegasus-isi/claude-plugin-marketplace --skill pr-pegasus-isi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This skill removes the friction and risk of manual pull request creation by automating branch pushing, CI validation, and standardized PR formatting.

Core Features & Use Cases

  • Automated CI Verification: Ensures end-to-end tests pass before allowing a PR to be opened, preventing broken code from reaching the main branch.
  • Standardized PR Metadata: Automatically assigns the user, links the PR to the relevant issue number based on branch naming conventions, and includes a summary of review findings.
  • Use Case: After completing a feature branch, use this skill to safely push your code and open a PR against the correct base branch, ensuring all quality gates are met without manual intervention.

Quick Start

Ask the assistant to open a pull request for the current branch targeting the main branch.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate GitHub pull request creation with CI checks?▼

You can automate GitHub pull request creation by validating CI status and branch integrity before pushing code. This enforces pre-merge testing and injects standardized PR metadata to prevent broken code from reaching the main branch.

Do I need the GitHub CLI to automate pull request workflows?▼

Yes, you need the GitHub CLI and local git configuration to automate pull request workflows. These dependencies are required to securely execute push and PR creation operations against your repository.

What is the best way to link a pull request to an issue automatically?▼

The best way to link a pull request to an issue automatically is by using branch naming conventions. The automation reads your branch name to link the relevant issue number and injects standardized PR metadata during creation.

Can I prevent merging broken code by validating CI status before opening a PR?▼

Yes, validating CI status before opening a PR prevents merging broken code. The automation ensures end-to-end tests pass before allowing a pull request to be opened, acting as a pre-merge quality gate.

How does standardized PR metadata injection work for GitHub workflows?▼

Standardized PR metadata injection works by automatically assigning the user, linking the relevant issue number based on branch naming conventions, and including a summary of review findings in the PR body.

Related Skills

Explore More Software Engineering Skills→
brainbrewlabsbrainbrewlabs
7

git

Coordinates Git commit, push, and PR actions via git-manager modes.

Official
Intermediate
kevindreekevindree

ci-cd-and-automation

Design and harden CI/CD pipelines with quality gates and deployment automation.

Community
Advanced
cbleckercblecker
5

creating-pull-request

Automate GitHub pull request creation with branch pushing and PR metadata.

Community
Basic
amo-tech-aiamo-tech-ai

cicd-pipeline

Automate GitHub Actions CI/CD pipelines for build, test, lint, and deployment workflows.

Community
Intermediate