pr

Create pull requests with branch, commit, and documentation checks.

2|Updated Aug 15, 2025

Search Tags:#git #code review #pull request #GitHub #PR automation

Ready to run

npx skills add https://github.com/rfhayn/forager --skill pr-rfhayn

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the creation of pull requests, ensuring they adhere to project conventions and are ready for review.

Core Features & Use Cases

Standardized PR Creation: Follows project-specific PR naming, body structure, and documentation freshness checks.
Branch and Commit Analysis: Provides details on the current branch, commits, and files changed.
Documentation Freshness Check: Ensures all necessary documentation is up-to-date before creating a PR.
Optional Quality Review: Offers additional checks for naming conventions, code quality, and secret scanning.

Quick Start

Run the 'create a PR' command or say 'let's PR this' to generate a pull request following project standards.

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 to follow project conventions?▼

Automating pull request creation involves enforcing standardized PR naming, body structure, and documentation checks. This ensures PRs adhere to project conventions and are ready for review by analyzing branch state and commit history.

Do I need GitHub CLI to create standardized pull requests?▼

Yes, GitHub CLI is required alongside Git to interact with the repository. These dependencies allow the automation to analyze commits, verify branch state, and create the pull request on GitHub.

What checks are performed before generating a pull request?▼

Before generating a pull request, checks are performed on branch state, commit history, and documentation freshness. Optional quality reviews can also check naming conventions, code quality, and scan for secrets.

Can I check documentation freshness as part of PR automation?▼

Yes, documentation freshness checks are a core feature of PR automation. This ensures all necessary documentation is verified as up-to-date before the pull request is created, maintaining project quality.

What is the best way to ensure PR quality and consistency across a team?▼

The best way to ensure PR quality is enforcing standardized formats with automated checks for branch state and commit history. Standardized PR creation ensures all team submissions follow project conventions consistently.