github-pr

Create and update GitHub Pull Requests via the GitHub CLI.

32.5k|4.9k|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/zeroclaw-labs/zeroclaw --skill github-pr-zeroclaw-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr
Source: https://github.com/zeroclaw-labs/zeroclaw/tree/main/.claude/skills/github-pr
Command: npx skills add https://github.com/zeroclaw-labs/zeroclaw --skill github-pr-zeroclaw-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of opening and updating GitHub Pull Requests, automating tasks like filling out PR templates, adding labels, and syncing descriptions with new commits.

Core Features & Use Cases

  • Open New PRs: Creates new PRs with a fully pre-filled body based on the repository's PR template.
  • Update Existing PRs: Edits titles, bodies, and labels of existing PRs, including smart updates after new commits.
  • Comment on PRs: Adds comments to PRs.
  • Use Case: After pushing new commits to your feature branch, use this skill to update the PR description to reflect the latest changes and ensure all required sections are addressed.

Quick Start

Use the github-pr skill to open a new pull request for the current branch.

Frequently Asked Questions about github-pr

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

FAQPage Schema
How do I automate GitHub Pull Request creation from a template?

Automating GitHub Pull Request creation involves using the GitHub CLI to open new PRs while automatically pre-filling the PR body from the repository's existing PR template. This ensures all required sections are addressed instantly without manual copy-pasting.

Can I update an existing pull request description after pushing new commits?

Yes, you can update an existing pull request description after pushing new commits. The process edits titles, bodies, and labels of existing PRs, including smart updates that sync descriptions to reflect the latest changes pushed to your feature branch.

Do I need the GitHub CLI installed to manage pull requests automatically?

Yes, you need the GitHub CLI installed to manage pull requests automatically. Full functionality requires both git and the gh CLI to execute commands for opening new PRs, modifying existing ones, and adding comments.

What's the best way to add labels to a pull request via command line?

The best way to add labels to a pull request via command line is using the GitHub CLI to automate label management. This approach handles label assignment during PR creation and can modify labels on existing pull requests without navigating the web interface.

How does automated pull request body syncing work with new commits?

Automated pull request body syncing works by detecting new commits pushed to your feature branch and automatically editing the existing PR description. This ensures the PR body accurately reflects the latest changes while maintaining the structure of the original PR template.

When should I not use automated pull request management scripts?

You should not use automated pull request management scripts if your environment lacks the GitHub CLI or git, as full functionality depends on these dependencies. Manual web interface updates are necessary without these tools installed locally.