pr

Create and manage GitHub pull requests with structured titles and descriptions.

95|4|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/try-works/role-model --skill pr-try-works
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/try-works/role-model/tree/main/.agents/skills/pr
Command: npx skills add https://github.com/try-works/role-model --skill pr-try-works

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of creating and updating GitHub pull requests, ensuring that PRs are well-structured, accurately reflect the changes, and adhere to the project's standards.

Core Features & Use Cases

  • Structured PR Creation: Offers a clear template for writing PR titles and descriptions, including best practices for summarizing changes and referencing related issues.
  • PR Editing Guidelines: Provides detailed instructions for editing existing PRs, ensuring that updates are accurate and maintain the PR's structure.
  • Branch and Title Formatting: Instructs on creating branches and titles that are consistent with the project's naming conventions.
  • Documentation Checklist: Ensures that all necessary documentation elements are included in PRs, such as changelogs and style guide adherence.

Quick Start

To create a new PR, run the 'create-pr' command and follow the on-screen prompts to fill out the PR title and description based on the provided template.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I create a structured GitHub pull request using the CLI?

To create a structured GitHub pull request, run the 'create_pr' command and follow the on-screen prompts to fill out the PR title and description based on structured guidelines. This ensures your PR accurately reflects changes and adheres to project standards.

What are the best practices for writing pull request titles and descriptions?

Best practices for pull request titles and descriptions include using a clear template for summarizing changes, referencing related issues, and maintaining branch and title formatting consistent with the project's naming conventions to ensure well-structured PRs.

Do I need GitHub CLI installed to manage pull requests with this Skill?

Yes, you need GitHub CLI (gh) installed and authenticated. The Skill requires GitHub CLI for authentication and to automate the operation of creating, editing, and updating pull requests based on repository standards.

Can I edit and update existing pull requests to match repository standards?

Yes, you can edit and update existing pull requests. The Skill provides detailed instructions for PR editing, ensuring that updates maintain the PR's structure, accurately reflect changes, and adhere to project documentation checklists.

What documentation elements should be included when creating a pull request?

When creating a pull request, you should include documentation elements such as changelogs and adherence to the style guide. The Skill provides a documentation checklist to ensure all necessary elements are present in your PRs.