skills.rest
TalonT-Org
TalonT-OrgOFFICIAL
Explore all skills by this author →
GitHub

open-pr

Create GitHub pull requests from plan files with architecture diagrams.

5|1|Updated Feb 18, 2026
Search Tags:#automation#ci/cd#code review#pull request#github#diagrams
One-click install
npx skills add https://github.com/TalonT-Org/AutoSkillit --skill open-pr-talont-org
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/TalonT-Org/AutoSkillit/tree/main/src/autoskillit/skills/open-pr
Command: npx skills add https://github.com/TalonT-Org/AutoSkillit --skill open-pr-talont-org

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of GitHub Pull Requests, including relevant architecture diagrams and issue closing, streamlining the code review process.

Core Features & Use Cases

  • Automated PR Creation: Generates PRs with titles derived from plan files and bodies populated with summaries, requirements, and architecture diagrams.
  • Architecture Diagram Integration: Selects relevant arch-lens lenses based on changed files and embeds generated diagrams in the PR body.
  • Issue Closing: Optionally closes a GitHub issue when the PR is created.
  • Use Case: After implementing a new feature, this Skill can be invoked to automatically create a PR, ensuring reviewers have all necessary context, including architectural impact, directly within the PR description.

Quick Start

Use the open-pr skill to create a pull request for the feature branch 'my-feature' against the base branch 'main', using plan files located at '/path/to/plan1.md'.

Frequently Asked Questions about open-pr

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

FAQPage Schema
How do I automate GitHub pull request creation with architecture diagrams?▼

You can automate pull request creation by parsing implementation plan files to identify changed files, selecting arch-lens lenses to generate architecture diagrams, and composing a PR body with summaries, requirements, and diagrams.

Can I automatically close a GitHub issue when creating a pull request?▼

Yes, you can automatically close a GitHub issue when creating a pull request by specifying the issue during PR generation, which optionally closes it once the PR is successfully created.

How does a pull request generator include architecture diagrams in the PR body?▼

A pull request generator includes architecture diagrams by selecting relevant arch-lens lenses based on the identified changed files and embedding the generated diagrams directly into the composed PR body.

Do I need implementation plan files to create a GitHub PR with diagrams?▼

Yes, implementation plan files are required to create a GitHub PR with diagrams, as the tool parses these files to derive the PR title, identify changed files, and populate the PR body.

Can I use multiple plan files to generate a single GitHub pull request?▼

Yes, you can use multiple plan files to generate a single GitHub pull request, as the tool explicitly handles both single and multiple plan files to compose the final PR body.

Related Skills

Explore More Software Engineering Skills→
DethonDethon
3

requesting-code-review

Generate reviewer-ready summaries of code changes with task details and changed files.

Community
Basic
SantiagoisperSantiagoisper

land-and-deploy

Merge pull requests, deploy code changes, and verify production readiness.

Community
Advanced
TalonT-OrgTalonT-Org
5

create-review-pr

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

Official
Advanced
paultyngpaultyng
9

ship-it

Automate Git pre-commit checks, changelog generation, and GitHub pull request updates.

Community
Advanced