pr

Generate pull request descriptions from git history and templates.

59|3|Updated Jan 23, 2020
One-click install
npx skills add https://github.com/michaeldyrynda/dotfiles --skill pr-michaeldyrynda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/michaeldyrynda/dotfiles/tree/main/agents/skills/pr
Command: npx skills add https://github.com/michaeldyrynda/dotfiles --skill pr-michaeldyrynda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR descriptions are a time-consuming requirement for code reviews and release notes; this Skill automates creating comprehensive PR bodies using git history context and template data to ensure clarity and consistency.

Core Features & Use Cases

  • Generate PR descriptions using git history context
  • Apply PR templates when forming the PR body
  • Supports typical PR workflows (feature, fix, doc updates) and template variations

Quick Start

Use the pr skill to generate a PR description from the current branch and open a PR with the appropriate template.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I generate a pull request description from git history?

This Skill generates comprehensive pull request descriptions by extracting context from repository history and applying templates. It integrates commit data from the current branch to produce review-ready PR bodies.

Can I use a PR template for feature branches and bug fixes?

Yes, the Skill applies PR templates across typical workflows including feature branches, bug fixes, and documentation updates. It adapts to different template formats to ensure consistent PR body generation.

What is the best way to automate pull request body creation for code reviews?

Automating pull request body creation is achieved by integrating git history context with repository templates. This approach ensures clarity and consistency for code reviews while reducing manual writing time.

Does this PR generation approach work without external dependencies?

This PR generation approach works without external dependencies. The Skill operates independently to extract git history and apply template data, requiring no additional components to generate descriptions.

Why are my automated PR descriptions missing context from previous commits?

Missing commit context in PR descriptions occurs when repository history is not properly integrated. This Skill resolves the issue by extracting and applying comprehensive git history context directly into template-based PR bodies.