pr-writer

Generate structured GitHub pull request descriptions with linked issues and validation steps.

Updated Oct 25, 2025
One-click install
npx skills add https://github.com/SoloXLab/perfetto-dsl --skill pr-writer-soloxlab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-writer
Source: https://github.com/SoloXLab/perfetto-dsl/tree/main/.agents/skills/pr-writer
Command: npx skills add https://github.com/SoloXLab/perfetto-dsl --skill pr-writer-soloxlab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Poorly written pull request descriptions leave reviewers without critical context about code changes, lead to unnecessary back-and-forth during review, and increase the risk of merging faulty code due to missing validation or rollback information. This Skill solves that by guiding you to create structured, complete PR descriptions that provide all the context reviewers need to efficiently approve changes.

Core Features & Use Cases

  • Structured Template Enforcement: Automatically ensures all required sections (linked issues, background, changes, validation, risk, rollback) are included in every PR description, so no critical information is omitted.
  • Quality Guardrails: Prevents vague descriptions, requires reproducible validation steps with paired commands and results, and mandates explicit risk and rollback details for delivery-focused changes.
  • Use Case: When submitting a code change to a team repository, use this Skill to generate a PR description that lets reviewers quickly understand the purpose of the change, how it was tested, and how to revert it if issues arise, cutting down review time and reducing merge risks.

Quick Start

Use the pr-writer skill to generate a complete, review-ready pull request description for your latest code changes, including all required context for your team's reviewers.

Frequently Asked Questions about pr-writer

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

FAQPage Schema
How do I write a good GitHub pull request description for code review?

To write a good pull request description, use a structured template that includes linked issues, change context, reproducible validation steps, risk assessment, and explicit rollback steps to speed up code reviews.

What should a PR description include to prevent slow code review workflows?

A PR description should include linked issues, background, specific changes, paired validation commands and results, risk assessment, and rollback steps to prevent slow code review workflows caused by missing context.

How do I generate a rollback plan for a GitHub pull request?

To generate a rollback plan for a pull request, document explicit rollback steps and risk assessments within the PR description, ensuring reviewers understand how to revert changes if validation fails.

Does this PR description generator work for feature, bugfix, and refactor changes?

Yes, this PR description generator works for feature, bugfix, and refactor changes submitted to version-controlled GitHub repositories, enforcing quality guardrails to ensure all critical validation and context is included.

Why are my pull request descriptions causing unnecessary back-and-forth during review?

Pull request descriptions cause unnecessary back-and-forth during review when they lack critical context, omit reproducible validation evidence, or miss explicit rollback details required by reviewers to efficiently approve changes.

Can I enforce a structured template for every pull request in my software engineering team?

Yes, you can enforce a structured template for every pull request to ensure required sections like linked issues, validation, risk, and rollback are included, eliminating inconsistent documentation across your software engineering team.