skills.rest
MAdrid1011
MAdrid1011COMMUNITY
Explore all skills by this author →
GitHub

open-pr

Create GitHub pull requests from conversation context with formatted titles and bodies.

1|2|Updated Sep 17, 2025
Search Tags:#automation#workflow#github#validation#pull-request#open-pr#tag-selection
One-click install
npx skills add https://github.com/MAdrid1011/Zircon-VLIW --skill open-pr-madrid1011
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/MAdrid1011/Zircon-VLIW/tree/main/.claude/skills/open-pr
Command: npx skills add https://github.com/MAdrid1011/Zircon-VLIW --skill open-pr-madrid1011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create GitHub pull requests from conversation context with proper formatting and tag selection.

Core Features & Use Cases

  • Generates PR titles and bodies that follow a prescribed structure, including sections like Summary, Changes, Testing, and Related Issue.
  • Enforces tag selection based on project conventions and requires an issue number when applicable.
  • Validates content against PR formatting rules and prompts for user confirmation before submission.

Quick Start

Provide the conversation context and PR details; the agent will generate a properly formatted PR.

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 from conversation context?▼

You can automate GitHub pull request creation by providing conversation context to an agent, which then generates a properly formatted PR with standardized sections like Summary, Changes, and Testing before prompting for user confirmation.

What is the required structure for generating a standardized GitHub pull request?▼

A standardized GitHub pull request requires a structured body featuring Summary, Changes, Testing, and Related Issue sections. It also enforces tag selection based on project conventions and mandates a valid issue number in the PR title.

How do I ensure my pull request includes the correct tags and issue references?▼

To ensure correct tags and issue references, the PR generation process validates content against formatting rules, enforces tag selection based on project conventions, and requires a valid issue number in the PR title before submission.

Do I need authenticated tooling to open a PR through an automated workflow?▼

Yes, you need authenticated tooling with access to a GitHub repository to open a PR through an automated workflow. The agent generates the formatted PR content and prompts for user confirmation before submitting it to the repository.

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

Yes, you can review the pull request content before submission. The agent validates the generated content against formatting rules and prompts for user confirmation to ensure the PR meets project standards before opening it on GitHub.

What are the limitations of automating pull request creation from a conversation?▼

Limitations include the strict requirement for a valid issue number in the PR title and adherence to prescribed tag selection conventions. Without authenticated GitHub repository access and proper conversation context, PR generation cannot proceed.

Related Skills

Explore More Software Engineering Skills→
NVIDIANVIDIA
8.1k

review-github-pr

Summarize GitHub pull request diffs and identify key design decisions.

Official
Advanced
tribedotruntribedotrun
8

mando-pr

Create GitHub pull requests and trigger AI reviewers with CI monitoring.

Official
Advanced
cassm199-mitacassm199-mita

github-operations

Automate GitHub branch naming, commits, and PR operations via MCP or gh CLI.

Community
Intermediate
dalawwadalawwa

git:create-pr

Create pull requests with GitHub CLI using repository templates and draft guidance.

Community
Intermediate