skills.rest
giruclawbot
giruclawbotCOMMUNITY
Explore all skills by this author →
GitHub

github-pr

Generate conventional commit PR titles and Summary/Changes/Testing descriptions.

Updated Mar 23, 2026
Search Tags:#git#pull request#github#code-review#conventional-commits#gh-cli#pr-template
One-click install
npx skills add https://github.com/giruclawbot/giru-backup --skill github-pr-giruclawbot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pr
Source: https://github.com/giruclawbot/giru-backup/tree/main/skills/github-pr
Command: npx skills add https://github.com/giruclawbot/giru-backup --skill github-pr-giruclawbot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent, vague, or oversized pull requests by providing clear conventions for titles, descriptions, and commit practices so maintainers can review and merge changes faster.

Core Features & Use Cases

  • Conventional Commit Titles: Enforce concise, machine-readable PR titles using conventional commit types and optional scopes to improve changelogs and automation.
  • Structured PR Descriptions: Provide a reusable Summary / Changes / Testing template and guidance for linking issues (Closes #123) to make intent and scope explicit.
  • Commit & PR Best Practices: Encourage atomic commits, draft PRs for WIP, and examples for adding reviewers and labels with the gh CLI to streamline review workflows.
  • Use Cases: Creating new feature PRs, preparing bugfix PRs with clear testing steps, splitting large changes into logical PRs, and drafting reviewer-ready descriptions before opening a PR.

Quick Start

Create a PR with a conventional-commit style title and a body that includes a concise Summary, a Changes list, a Testing checklist, and an issue link using Closes #<issue>.

Frequently Asked Questions about github-pr

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

FAQPage Schema
How do I write a conventional commit pull request title for GitHub?▼

A conventional commit pull request title uses concise, machine-readable types and optional scopes to improve changelogs and automation. It clearly communicates intent, such as adding a feature or fixing a bug, making reviews faster.

Can I add reviewers and labels to a pull request using gh CLI?▼

Yes, you can add reviewers and labels to a pull request using gh CLI commands. This streamlines review workflows by automating the assignment of reviewers and applying categorical labels directly from the terminal.

What is the best way to prepare a review-ready pull request for a large refactor?▼

The best way to prepare a review-ready pull request for a large refactor is to split oversized changes into logical, atomic commits. Drafting the PR with a structured description ensures clear scope before opening it for review.

How do I link a GitHub issue to a pull request description?▼

To link a GitHub issue to a pull request description, add a closing keyword like Closes #123 in the body. This connects the pull request to the issue, automatically closing the issue upon merge.

Related Skills

Explore More Software Engineering Skills→
mycelium-iomycelium-io
112

ship

Automate precommit checks, staging, conventional commits, and optional pushes.

Official
Intermediate
N4M3ZN4M3Z
3

GitHub

Manage GitHub repositories, releases, pull requests, and Actions via gh CLI.

Community
Advanced
DataRecceDataRecce
470

claude-code-review

Review GitHub pull requests and post comments with test and linter evidence.

Official
Advanced
djnsty23djnsty23
2

commit

Automates Git commit, push and pull-request workflows with conventional commit enforcement and pre-push validation.

Community
Advanced