pr

Create, review, and merge GitHub pull requests via the GitHub API.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gonzoblasco/club-camping-lobos --skill pr-gonzoblasco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/gonzoblasco/club-camping-lobos/tree/main/.agents/skills/pr
Command: npx skills add https://github.com/gonzoblasco/club-camping-lobos --skill pr-gonzoblasco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of creating a pull request, running a code review, and merging it, ensuring a formal closure for each task.

Core Features & Use Cases

  • Pull Request Creation: Automatically creates a pull request with structured description, commits, and push.
  • Code Review: Initiates code review with predefined commands for easy verification.
  • Merging: Merges pull requests after review approval, maintaining commit history.

Quick Start

Use the /pr command to initiate the pull request creation process for the 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 pull request creation and merging on GitHub?

Automating pull request creation and merging is handled by utilizing the GitHub API to create PRs, execute code reviews, and perform merges for the current branch. You can initiate this structured process using the /pr command.

Do I need to install any dependencies to automate the pull request lifecycle?

Yes, automating the pull request lifecycle requires the curl command-line tool to be installed. You also need appropriate environment variables configured for GitHub API authorization and repository access.

Can I run a code review automatically before merging a pull request?

Running a code review before merging is supported through predefined commands for easy verification. The Skill initiates the code review process and merges the pull request after review approval while maintaining commit history.

What is the best way to structure code review and merge processes for GitHub repositories?

The best way to structure code review and merge processes is to automate the entire pull request lifecycle with structured descriptions, commits, and pushes. This ensures formal closure for each task through automated creation, review, and merging via the GitHub API.

Does the automated pull request process work with existing CI/CD pipelines?

The automated pull request process integrates with GitHub repositories using the GitHub API and requires environment variables for authorization. It handles PR creation, review, and merging, which can complement existing CI/CD workflows.