create-review-pr

Create an integration pull request from a JSON list of collapsed PRs.

5|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/TalonT-Org/AutoSkillit --skill create-review-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-review-pr
Source: https://github.com/TalonT-Org/AutoSkillit/tree/main/src/autoskillit/skills/create-review-pr
Command: npx skills add https://github.com/TalonT-Org/AutoSkillit --skill create-review-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation of integration Pull Requests by automatically compiling details from multiple smaller PRs, generating architectural diagrams, and ensuring all relevant issue closures are carried forward.

Core Features & Use Cases

  • Automated PR Body Generation: Creates a comprehensive PR description including a summary of merged PRs, audit verdicts, and architectural impact diagrams.
  • Cross-Referencing: Automatically includes Closes #N and Fixes #N references from original PRs to ensure linked issues are closed upon merge.
  • Architectural Visualization: Generates diagrams using Arch-Lens to help reviewers understand the impact of changes.
  • Use Case: After merging several feature branches into an integration branch, use this Skill to create a single, well-documented PR that represents the combined changes, complete with visual aids and issue tracking.

Quick Start

Use the create-review-pr skill to create an integration PR for the 'main' branch, using the 'pr-batch/feature-set-1' integration branch and the 'pr_order.json' file.

Frequently Asked Questions about create-review-pr

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

FAQPage Schema
How do I create an integration pull request from multiple smaller PRs?▼

To create an integration pull request, this skill parses a JSON file detailing individual PRs, compiles their summaries, and uses GitHub CLI to generate a comprehensive PR into a target branch.

How does an integration pull request carry over closing references from original PRs?▼

An integration pull request automatically fetches and includes `Closes #N` and `Fixes #N` references from original PR bodies, ensuring linked issues are properly closed upon merging the integration branch.

Can I generate architectural diagrams for a GitHub pull request automatically?▼

Yes, this skill generates architectural diagrams using Arch-Lens to help reviewers understand the impact of changes, embedding the visualizations directly within the pull request body.

What is the best way to close original PRs after creating an integration branch?▼

After creating the integration PR via GitHub CLI, the skill automatically closes the original PRs with a comment linking to the new integration PR, ensuring clean repository tracking.

Do I need a specific JSON format to automate pull request generation?▼

Yes, you must provide a JSON file detailing the individual collapsed PRs and their order, which the skill parses to construct the detailed integration PR body and fetch closing references.