skills.rest
DIO0550
DIO0550COMMUNITY
Explore all skills by this author →
GitHub

pull-request

Generate PR descriptions and checklists from code changes and issue references.

1|Updated Dec 21, 2025
Search Tags:#automation#git#template#code-review#pull-request#pr-description
One-click install
npx skills add https://github.com/DIO0550/d-market --skill pull-request-dio0550
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/DIO0550/d-market/tree/main/plugins/git-workflow-plugin/skills/pull-request
Command: npx skills add https://github.com/DIO0550/d-market --skill pull-request-dio0550

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

PR descriptions and change summaries often require repetition and alignment with templates; this skill generates concise, template-driven descriptions to streamline code reviews.

Core Features & Use Cases

  • Generate PR descriptions aligned with the standard PR template.
  • Classify changes into types (e.g., bugfix, feature, refactor) with emoji labels.
  • Include linked issues and a ready-to-use checklists for reviewers.

Quick Start

Describe the patch succinctly by providing a short summary, selecting a change type, and listing related issues and checks.

Frequently Asked Questions about pull-request

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

FAQPage Schema
How do I generate a pull request description from code changes?▼

To generate a pull request description, provide a patch summary, select a change type, and list related issues. The skill produces a template-driven PR summary with classified change types and a reviewer checklist to streamline code reviews.

What should a PR template include for GitHub code reviews?▼

A PR template for GitHub code reviews should include change type classification, linked issue references, and a comprehensive checklist. This ensures consistent, template-driven documentation across feature integrations, bugfixes, and refactoring workflows.

Can I classify git changes into types like bugfix or feature automatically?▼

Yes, you can classify git changes into types like bugfix or feature by providing a short summary of your patch. The skill applies emoji labels and categorizes the changes to align with standard PR templates for consistent reviewing.

How do I add a reviewer checklist to my pull request?▼

To add a reviewer checklist to your pull request, input your code changes and issue references. The skill generates a ready-to-use checklist within the PR description, ensuring reviewers can systematically verify feature integrations and documentation updates.

Do I need to link issues in my PR description for code review automation?▼

Linking issues in your PR description is required for code review automation. The skill uses these issue references alongside code changes to generate comprehensive, template-driven summaries that encapsulate requirements and speed up the review process.

What is the best way to standardize PR descriptions across multiple repositories?▼

The best way to standardize PR descriptions across multiple repositories is using a template-driven approach. This skill generates consistent summaries with change type classification, linked issues, and checklists, ensuring uniform documentation across Git and GitHub workflows.

Related Skills

Explore More Software Engineering Skills→
tailcallhqtailcallhq
7.5k

github-pr-description

Generate pull request descriptions from git diffs and commit history.

Official
Intermediate
BillChiricoBillChirico
5

github-pr-resolver

Resolve GitHub pull request review threads and failing CI checks with commits.

Community
Advanced
yolo-labs-hqyolo-labs-hq

git-workflow

Enforce conventional commits, branch naming, and PR structure in Git workflows.

Official
Intermediate
stacklokstacklok
2.0k

pr-inline-review

Submit inline review comments and code suggestions to GitHub Pull Requests via gh CLI.

Official
Intermediate