pr

Automate pull request preparation with validation, syncing, and preflight checks.

Updated Feb 8, 2026

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

Ready to run

npx skills add https://github.com/eivindeb/agent-skills --skill pr-eivindeb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/eivindeb/agent-skills/tree/main/PR
Command: npx skills add https://github.com/eivindeb/agent-skills --skill pr-eivindeb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of preparing and creating pull requests by automating validation, syncing, preflight checks, and command execution.

Core Features & Use Cases

Automated PR Creation: Validates branch state, syncs with main, runs tests, and creates a GitHub PR.
Robust Validation: Enforces branch naming conventions, checks remote configurations, and ensures a clean working tree.
Use Case: After committing your feature work, use this skill to automatically handle all the necessary steps to get your pull request ready for review.

Quick Start

Use the pr skill to prepare and create a pull request for the current feature 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 from a feature branch?▼

Automating pull request creation involves validating your branch state, syncing with the main remote, running preflight checks, and executing push and gh PR commands. This skill handles all these steps automatically after you commit your feature work.

Can I create a GitHub PR using a fork repository model?▼

Yes, you can create a GitHub PR using a fork repository model. This skill handles both fork and single-remote repository models, applying configurable authentication scopes to ensure correct remote syncing before submission.

What preflight checks are required before submitting a pull request?▼

Preflight checks for pull requests include validating guardrails, enforcing branch naming conventions, checking remote configurations, and ensuring a clean working tree. The process also verifies branch context and reviews documentation before executing PR commands.

Why does my pull request validation fail with a dirty working tree?▼

Pull request validation fails with a dirty working tree because the preflight checks enforce a clean state before submission. You must commit or stash uncommitted changes to ensure branch context validation and remote syncing can execute successfully.

Does this PR automation tool work with CI/CD pipelines and Git guardrails?▼

Yes, this PR automation tool works with CI/CD pipelines and Git guardrails by validating configured guardrails and running preflight checks before pushing. It ensures your code review submission aligns with automation standards and remote configurations.