pull-request

Generate pull request descriptions from commit history and code changes.

Updated Aug 23, 2026

Search Tags:#automation #git #developer tools #code review #documentation #pull request

Ready to run

npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill pull-request-reeinharddd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/reeinharddd/impulsa-monorepo/tree/main/.github/skills/pull-request
Command: npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill pull-request-reeinharddd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive pull request descriptions, ensuring all necessary information is included for effective code reviews.

Core Features & Use Cases

Automated Description Generation: Creates detailed PR descriptions based on commit messages and code changes.
Standardized Template: Enforces a consistent PR template including type of change, testing status, and related issues.
Use Case: When a developer pushes a new feature branch for review, this Skill automatically drafts a PR description that summarizes the commits, categorizes the changes, and prompts for testing and issue linking.

Quick Start

Use the pull-request skill to generate a description for the current pull request.

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 commit history?▼

To generate a pull request description, this Skill analyzes your commit messages, changed file lists, and related issue information. It automatically drafts a comprehensive summary that categorizes code changes for review on platforms like GitHub.

Can I standardize my GitHub pull request templates automatically?▼

Yes, you can standardize GitHub pull request templates automatically. This Skill enforces a consistent PR template that includes the type of change, testing status, and related issues for every generated description.

What information do I need to provide to automate PR description creation?▼

To automate PR description creation, you need to provide access to commit data, changed file lists, and related issue information. This data allows the Skill to summarize commits and categorize code changes effectively.

Does this tool work with my existing developer automation workflow?▼

This tool integrates with developer automation workflows by using commit history and code changes to draft summaries. It operates without external dependencies, relying solely on your git commit data and file changes to generate the required documentation.

What is the best way to draft a comprehensive PR summary for a new feature branch?▼

The best way to draft a comprehensive PR summary is to apply this Skill to your new feature branch. It automatically summarizes commits, categorizes the changes according to a standardized template, and prompts for testing and issue linking.

Are there limitations to generating code review documentation from commit messages?▼

A limitation of generating code review documentation from commit messages is that the output relies entirely on the quality of your commit data and changed file lists. It cannot infer context or testing status without explicit issue information.