do-pr

Name: do-pr
Availability: InStock
Author: lushly-dev

Push a local branch and generate a structured pull request description.

4|1|Updated Dec 30, 2025

Search Tags:#automation #git #developer tools #code review #pull request #github

Ready to run

npx skills add https://github.com/lushly-dev/afd --skill do-pr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: do-pr
Source: https://github.com/lushly-dev/afd/tree/main/.claude/skills/do-pr
Command: npx skills add https://github.com/lushly-dev/afd --skill do-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of submitting code for review by automating the creation of pull requests, ensuring all necessary checks and information are included.

Core Features & Use Cases

Automated Branch Pushing: Pushes your local branch to the remote repository.
Intelligent PR Description Generation: Creates a structured PR description based on commit messages, diffs, and linked issues.
Reviewer Suggestion: Recommends reviewers based on file ownership (CODEOWNERS).
Use Case: After completing a feature and running local tests, use this Skill to push your branch and open a PR with a detailed description and appropriate labels, ready for your team's review.

Quick Start

Use the do pr skill to push your current branch and create a pull request for review.

Frequently Asked Questions about do-pr

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

FAQPage Schema

How do I automate pull request creation from local commits?▼

Automating pull request creation involves pushing a local branch to a remote repository and generating a structured description from commit history and diffs. This process verifies branch readiness and identifies linked issues automatically.

What's the best way to generate pull request descriptions from git diffs?▼

Generating pull request descriptions from git diffs uses commit messages and file changes to create a structured summary. It automatically identifies linked issues and suggests reviewers based on file paths to streamline code review.

Can I suggest reviewers automatically based on file paths for a pull request?▼

Suggesting reviewers automatically based on file paths relies on file ownership rules, such as CODEOWNERS. The automation scans modified file paths during pull request creation to recommend the appropriate reviewers for the code changes.

Does the automated pull request process work with GitHub CLI?▼

The automated pull request process integrates directly with GitHub CLI for PR creation. It uses the GitHub CLI to push branches, apply automated labels, and open the pull request with the generated structured description.

How do I verify branch readiness before pushing a local git branch?▼

Verifying branch readiness before pushing a local git branch is an automated step that checks the local state prior to remote submission. It ensures the branch is prepared for pull request creation by validating commit history and linked issues.

Can I apply automated labeling to pull requests based on commit history?▼

Applying automated labeling to pull requests based on commit history is supported during PR creation. The automation analyzes the commit diffs and linked issues to assign appropriate labels before opening the pull request for review.