Verified:GitHub

pr

Format, lint, test, push changes, and create pull requests on GitHub and GitLab.

3|2|Updated Apr 10, 2026

Search Tags:#automation #git #pr #lint #format #pull-request #tests

One-click install

npx skills add https://github.com/AdamCaviness/agentic-toolkit --skill pr-adamcaviness

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/AdamCaviness/agentic-toolkit/tree/main/skills/pr
Command: npx skills add https://github.com/AdamCaviness/agentic-toolkit --skill pr-adamcaviness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end PR workflow, reducing manual steps and human error when preparing and publishing code changes.

Core Features & Use Cases

End-to-end PR automation: formats, lints, runs tests, commits, and pushes changes, then creates a pull request.
Branch- and workflow-aware: detects non-main branches, handles branches ahead/behind main, and extracts issue numbers from branch names.
PR metadata & updates: creates or updates PRs with concise titles and structured bodies, including a brief summary of changes and testing notes.

Quick Start

Run /pr after finishing work on a feature branch to automatically format, lint, test, push, and open the PR for review.

Frequently Asked Questions about pr

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

FAQPage Schema

How do I automate formatting, testing, and opening a pull request in one step?▼

Automating pull request preparation is done by running a single command that formats, lints, tests, commits, pushes changes, and opens the PR. This end-to-end workflow operates on feature branches to reduce manual steps and human error.

Does automated PR creation work with both GitHub and GitLab repositories?▼

Automated PR creation works with GitHub, GitLab, and compatible platforms. The workflow detects non-main branches, extracts issue numbers from branch names, and generates concise PR metadata and structured body content across these Git-based platforms.

What is the best way to extract issue numbers from a feature branch name during PR creation?▼

Extracting issue numbers during PR creation is handled automatically by parsing the feature branch name. The workflow detects the branch, extracts the associated issue number, and incorporates it into the generated PR metadata and structured body content.

How do I update an existing pull request after pushing new code changes?▼

Updating an existing pull request is supported automatically when pushing additional code changes. The workflow formats, lints, tests, and pushes the new commits, then updates the open PR with concise titles and structured body content.

Can I run lint and format checks on a branch that is behind main before pushing?▼

Lint and format checks run on branches that are ahead or behind main. The workflow is branch-aware, applying formatting and linting to your current feature branch before running tests, committing, and pushing the changes to create a pull request.

Why should I automate branch handling instead of manually creating pull requests?▼

Automating branch handling reduces manual steps and human error when preparing and publishing code changes. It manages feature-branch workflows by automatically formatting, testing, pushing, and generating structured PR metadata, ensuring consistent preparation.