pr-review-packager

Generate structured pull requests from git history, issues, and ADRs.

Updated Apr 12, 2026

Search Tags:#automation #git #workflow #documentation #pull request #github

Ready to run

npx skills add https://github.com/olivermorgan2/workflow-generator --skill pr-review-packager

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-review-packager
Source: https://github.com/olivermorgan2/workflow-generator/tree/main/skills/pr-review-packager
Command: npx skills add https://github.com/olivermorgan2/workflow-generator --skill pr-review-packager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill removes the manual friction of drafting pull requests by automatically aggregating branch history, issue references, and design decisions into a standardized, professional format.

Core Features & Use Cases

Automated PR Packaging: Generates a complete PR body by pulling data from commit history, branch names, and ADRs.
Cross-Skill Continuity: Automatically carries forward design questions from previous issue execution sessions into the new PR.
Safety-First Workflow: Implements a mandatory approval gate, ensuring the user reviews and confirms the generated PR content before any public action is taken.

Quick Start

Invoke the pr-review-packager skill to automatically draft and open a pull request for your current feature branch.

Frequently Asked Questions about pr-review-packager

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

FAQPage Schema

How do I automate pull request creation from git history and branch metadata?▼

Automating pull request creation involves parsing branch metadata, commit history, and architectural decision records to generate a standardized PR body. This process aggregates design questions and issue references, ensuring consistent documentation before submission.

Does the PR generation workflow require the GitHub CLI to open pull requests?▼

Yes, authenticated pull request creation requires the GitHub CLI. The workflow uses the CLI to execute public-facing PR submissions remotely while maintaining strict user-approval gates to review the generated content beforehand.

How do architectural decision records integrate into automated pull request documentation?▼

Architectural decision records integrate into automated pull request documentation by cross-referencing design documentation with branch history. This aggregates structural context and issue tracking data directly into the PR body for research and software projects.

Can I review the generated pull request content before it is submitted to GitHub?▼

Yes, a mandatory approval gate ensures you review and confirm the generated pull request content before any public action. This safety-first workflow prevents unreviewed automated submissions from reaching your remote repository.

What is the best way to standardize pull request formatting for consistent delivery workflows?▼

Standardizing pull request formatting is achieved by aggregating branch names, commit history, and issue tracking references into a professional template. This removes manual friction and enforces a consistent delivery workflow across software projects.

How does cross-skill continuity carry forward design questions into a new pull request?▼

Cross-skill continuity carries forward design questions by automatically extracting context from previous issue execution sessions and integrating it into the new pull request body during the automated generation phase.