pr

Automates GitHub pull request creation and updating with pre-push validation and quality gates.

1|Updated Dec 1, 2025

Search Tags:#automation #git #ci/cd #code review #pull request #github

Ready to run

npx skills add https://github.com/hypeJunction/ai-assistant-starter --skill pr-hypejunction

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/hypeJunction/ai-assistant-starter/tree/main/skills/pr
Command: npx skills add https://github.com/hypeJunction/ai-assistant-starter --skill pr-hypejunction

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of creating and updating GitHub Pull Requests, ensuring they are well-documented, validated, and meet quality standards before submission.

Core Features & Use Cases

Pre-push Validation: Automatically runs tests, linters, and security scans to catch issues early.
Duplicate PR Prevention: Checks for existing PRs on the branch and offers to update them.
Comprehensive Documentation: Generates a detailed PR body including summary, changes, and test plans.
Use Case: After completing a new feature, you can invoke this Skill to automatically run all checks, ensure your code is clean, and create a professional PR ready for review, even handling the case where you might have pushed a draft earlier.

Quick Start

Use the pr skill to create a new pull request for your 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 GitHub pull request creation with pre-push validation?▼

Automating GitHub pull request creation involves running tests, linters, and security scans before pushing changes. This Skill enforces those quality gates and requires explicit user confirmation before submitting the validated code to GitHub.

What is the best way to update an existing GitHub pull request instead of creating a duplicate?▼

To update an existing GitHub pull request, the system checks for active PRs on your current branch and offers to update them. This prevents duplicate pull requests and appends comprehensive documentation to the original submission.

How does automated code review integrate into CI/CD pull request workflows?▼

Automated code review integrates into CI/CD pull request workflows by executing security scans and linters as pre-push validation. This ensures code meets quality standards before the GitHub pull request is formally created or updated.

Can I generate comprehensive PR descriptions automatically for my current Git branch?▼

Yes, you can generate comprehensive PR descriptions automatically. The Skill analyzes your Git branch and produces a detailed pull request body including a summary of changes, specific modifications, and test plans.

Do I need to run linters and tests manually before creating a pull request?▼

You do not need to run linters and tests manually before creating a pull request. The automation performs pre-push validation by executing these checks automatically and requiring explicit confirmation before pushing any changes.

Why does my pull request automation require explicit confirmation before pushing code?▼

Pull request automation requires explicit confirmation before pushing code to ensure human oversight. After running automated tests, linters, and security scans, the system pauses to let you review validation results before submitting changes to GitHub.