create-pr

Generate user-focused PR descriptions with Linear ticket references and screenshot prompts.

164|44|Updated Jun 30, 2023

Search Tags:#workflow #documentation #frontend #communication #pr #pull-request #user-value

Ready to run

npx skills add https://github.com/hivemq/hivemq-edge --skill create-pr-hivemq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/hivemq/hivemq-edge/tree/main/hivemq-edge-frontend/.claude/skills/create-pr
Command: npx skills add https://github.com/hivemq/hivemq-edge --skill create-pr-hivemq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing PR descriptions that clearly communicate user value and testing expectations can be time-consuming and error-prone. This guide helps teams create consistent, value-driven PR bodies that streamline review and collaboration.

Core Features & Use Cases

Focus PR descriptions on user benefits to improve reviewer understanding and adoption.
Guide alignment with project processes, including links to related Linear issues and notes about UI changes needing screenshots.
Provide a structured PR template that reduces miscommunication and speeds up reviews across frontend and cross-team changes.

Quick Start

Draft a PR description that clearly communicates user value and testing expectations.

Frequently Asked Questions about create-pr

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

FAQPage Schema

How do I write a PR description that clearly communicates user value for frontend changes?▼

To write a PR description that communicates user value, use a structured template that highlights user benefits, outlines testing expectations, and links to related Linear tickets to streamline reviews for frontend changes.

What should be included in a pull-request body for UI updates?▼

A pull-request body for UI updates should include a structured narrative of user benefits, reference related Linear tickets, and attach screenshots before submitting to ensure reviewers can visually verify the changes.

Can I use this structured PR template for cross-cutting improvements beyond frontend changes?▼

Yes, you can use this structured PR template for cross-cutting improvements as it enforces a value-driven narrative and clear testing expectations, reducing miscommunication and speeding up reviews across cross-team changes.

What is the best way to structure a pull-request description to speed up code reviews?▼

The best way to structure a pull-request description is to enforce a consistent template that focuses on user benefits, documents testing expectations, and prompts for screenshots when UI changes are included to reduce miscommunication.

Do I need to link Linear tickets when writing a PR description for cross-team changes?▼

You should link related Linear tickets when writing a PR description for cross-team changes to guide alignment with project processes and provide reviewers with direct context for the value-driven updates.

Why does my PR template require screenshots for UI updates before submitting?▼

Your PR template requires screenshots for UI updates before submitting to provide visual verification of the user-focused changes, ensuring reviewers can accurately validate the frontend improvements and user benefits.