skills.rest
Zegocover
ZegocoverOFFICIAL
Explore all skills by this author →
WebsiteGitHub

zego-create-pr

Create GitHub pull requests from task specs using GitHub CLI.

1|3|Updated Jan 30, 2018
Search Tags:#code review#pull request#GitHub#PR automation#task specification
One-click install
npx skills add https://github.com/Zegocover/techops-tf_aws_metadata --skill zego-create-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zego-create-pr
Source: https://github.com/Zegocover/techops-tf_aws_metadata/tree/main/.claude/skills/zego-create-pr
Command: npx skills add https://github.com/Zegocover/techops-tf_aws_metadata --skill zego-create-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of creating GitHub pull requests for completed implementations, adhering to Zego's PR standards, and eliminates manual errors in the process.

Core Features & Use Cases

  • Automated PR Creation: Automatically opens GitHub pull requests based on the completion of an implementation.
  • Validation of Inputs: Ensures all required inputs are present and valid before creating the PR.
  • PR Title and Body Generation: Constructs the PR title and body using information from the task spec and other inputs.
  • Template-based PR Structure: Uses a template or default structure to organize the PR body with sections like Background, Changes, and Jira Ticket/s.

Quick Start

Run the 'zego-create-pr' skill with the necessary inputs, such as ticket key, branch, and task spec path.

Frequently Asked Questions about zego-create-pr

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

FAQPage Schema
How do I automate GitHub pull request creation from a task specification?▼

Automating GitHub pull request creation from a task specification requires parsing the task spec to derive objectives, validating inputs, and generating the PR title and body before submission via GitHub CLI.

What is the best way to ensure my pull requests comply with Zego's PR standards?▼

To ensure pull requests comply with Zego's PR standards, you can use an automated PR creation process that constructs the PR body using a default template with specific sections like Background, Changes, and Jira Ticket.

Do I need the GitHub CLI installed to automate PR submission?▼

Yes, you need the GitHub CLI installed to automate PR submission, as the process validates required inputs, generates the title and body from artifacts, and submits the pull request using the gh command line tool.

How does automated PR generation handle design doc artifacts?▼

Automated PR generation handles design doc artifacts by applying specific extraction logic to pull ticket information and derive the objective and goal directly for the pull request body structure.

What inputs are required to open a GitHub pull request automatically?▼

To open a GitHub pull request automatically, you must provide required inputs such as the ticket key, the target branch, and the task spec path, which are validated before PR title and body generation.

Can I validate ticket keys and branches before generating a pull request?▼

Validating ticket keys and branches before generating a pull request is a core feature of PR automation, ensuring all required inputs are present and valid before constructing the PR title and submitting via GitHub CLI.

Related Skills

Explore More Software Engineering Skills→
NIMBUS-MXNIMBUS-MX

ticket-brief

Generate work briefs with goals, acceptance criteria, and commit prefixes from ClickUp, Linear, GitHub tickets.

Official
Intermediate
BaqiF2BaqiF2
3

merge-pr

Merge GitHub Pull Requests after CI checks and code review pass.

Community
Advanced
JaviMalignoJaviMaligno
1

commit-pr

Generate commit messages, PR titles, and branch names from an issue URL.

Community
Intermediate
joaquimscostajoaquimscosta
21

creating-pr

Create GitHub pull requests from feature branches using the GitHub CLI.

Community
Advanced