pull-request

Create pull requests with English titles and bodies grouped by commit themes.

Updated May 21, 2026
One-click install
npx skills add https://github.com/shades-of-web/skills --skill pull-request-shades-of-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/shades-of-web/skills/tree/main/skills/pull-request
Command: npx skills add https://github.com/shades-of-web/skills --skill pull-request-shades-of-web

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The default pull request creation process often results in poorly structured PRs with a lack of context and reasoning. This skill solves this by enforcing a format that emphasizes the 'why' behind the changes and promotes clear communication.

Core Features & Use Cases

  • Structured PR Format: Ensures PR titles and descriptions are in English, grouped by themes, and focus on the rationale.
  • Branch Verification: Checks and confirms that the current branch is pushed before creating the PR.
  • Commit Analysis: Groups commits by logical themes for a better overview of changes.
  • English-only Communication: Requires English for PR titles and descriptions for clarity and consistency.
  • Bucketplace PR Labeling: Automatically adds the 'PR-by-AI' label for bucketplace organization repos.

Quick Start

Create a pull request with the pull-request skill and follow the structured guidelines for PR creation.

Frequently Asked Questions about pull-request

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

FAQPage Schema
How do I create a structured pull request with grouped commits on GitHub?

To create a structured pull request, the skill analyzes your commit history, groups commits by logical themes, and generates an English PR title and body focusing on the rationale behind your changes.

Why does my pull request lack context and reasoning for code review?

Pull requests often lack context because default creation processes do not enforce structured communication. This skill solves this by requiring a format that emphasizes the 'why' behind changes and groups commits by themes.

Do I need to push my branch to GitHub before generating a pull request?

Yes, you need to push your branch to GitHub first. The skill includes branch verification to check and confirm that the current branch is pushed to the remote repository before initiating PR creation.

Can I automatically add labels to my pull request using GitHub CLI?

Yes, you can automatically add labels to your pull request. The skill handles GitHub CLI operations and automatically adds the 'PR-by-AI' label for repositories within the bucketplace organization.

What is the best way to ensure English-only communication in pull request descriptions?

The best way to ensure English-only communication is to use a structured PR creation process that strictly requires English for both pull request titles and descriptions, ensuring clarity and consistency.