pr-builder

Draft reviewer-ready PR titles and bodies from branch diffs and test results.

3|1|Updated Feb 19, 2026

Search Tags:#automation #templates #documentation #pull request #qa #verification #pr

Ready to run

npx skills add https://github.com/zazzcode/zazz-skills --skill pr-builder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-builder
Source: https://github.com/zazzcode/zazz-skills/tree/main/.agents/skills/pr-builder
Command: npx skills add https://github.com/zazzcode/zazz-skills --skill pr-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating clear, reviewer-ready PR content from changes, verification evidence, and governing specs to accelerate code review and approval.

Core Features & Use Cases

Generates PR title and body aligned with the governing SPEC/PLAN.
Attaches or references the primary work item link and related context near the top.
Distills automated test results, manual validation notes, and acceptance criteria into reviewer-friendly sections.
Adheres to repo templates and repo-specific extensions when present to ensure consistency across PRs.

Quick Start

Provide the current branch, diff, and verification evidence to generate a ready PR draft.

Frequently Asked Questions about pr-builder

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

FAQPage Schema

How do I draft a pull request from my current branch and verification evidence?▼

To draft a pull request, provide your current branch, diff, and verification evidence. The system compiles a PR title and body with governing context, acceptance-criteria traceability, and manual validation notes into a ready-to-submit draft.

What is the best way to generate reviewer-ready PR content from automated test results?▼

Generating reviewer-ready PR content involves distilling automated test results and acceptance criteria into reviewer-friendly sections. It aligns the PR body with the governing SPEC/PLAN and repository templates to accelerate code review and approval.

Can I use repository templates and extensions to format my pull request body?▼

Yes, you can use repository templates and extensions. The system adheres to repo templates and repo-specific extensions when present, ensuring consistency across pull requests while compiling the required governing context and validation notes.

How do I trace acceptance criteria and work item links in a PR description?▼

To trace acceptance criteria, the PR description attaches the primary work item link near the top and distills the criteria into reviewer-friendly sections. This provides clear traceability linked to the governing SPEC/PLAN.

What inputs do I need to compile a ready-to-submit PR draft with acceptance-criteria traceability?▼

You need the primary work item link, diff/commits, test results, and domain-specific verification. These inputs allow the system to compile a ready-to-submit PR draft with acceptance-criteria traceability and manual validation notes.

Does the generated PR draft include manual validation notes alongside automated test results?▼

Yes, the generated PR draft includes manual validation notes alongside automated test results. It distills both into reviewer-friendly sections within the PR body, ensuring comprehensive verification evidence is presented for code review.