create-pr

Name: create-pr
Availability: InStock
Author: cartridge-gg

Creates or updates a GitHub Pull Request from the current branch to main.

11|6|Updated Apr 11, 2024

Search Tags:#automation #git #github #pr #code-review #ci #pull-request

Ready to run

npx skills add https://github.com/cartridge-gg/nums --skill create-pr-cartridge-gg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/cartridge-gg/nums/tree/main/.agents/skills/create-pr
Command: npx skills add https://github.com/cartridge-gg/nums --skill create-pr-cartridge-gg

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the workflow of creating or updating a pull request from the current branch to main, with built-in CI monitoring and feedback handling.

Core Features & Use Cases

Create or update a PR from the current branch to main, tracking status and upstream branch alignment.
Monitor CI checks and surface feedback to keep development moving without manual PR administration.
Use Case: When finishing a feature branch, run this Skill to open a PR against main and automatically watch CI results for quick iteration.

Quick Start

Run the create-pr workflow from your feature branch to main to open or update a PR and begin CI monitoring.

Frequently Asked Questions about create-pr

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

FAQPage Schema

How do I automate pull request creation from a feature branch to main?▼

You can automate pull request creation by running a workflow that reads your current git state, determines if a PR already exists, and creates or updates the pull request against the main branch using gh CLI commands and GraphQL mutations.

Can I monitor CI checks automatically after opening a GitHub pull request?▼

Yes, you can monitor CI checks automatically after opening a GitHub pull request. The automation surfaces CI feedback and tracks check statuses to keep development moving without requiring manual PR administration.

Do I need the gh CLI to automate GitHub PR updates and CI monitoring?▼

Yes, you need the gh CLI installed to automate GitHub PR updates and CI monitoring. The Skill depends on gh CLI commands and GraphQL mutations to read git state, determine PR existence, and track CI check results.

What is the best way to update an existing pull request instead of creating a duplicate?▼

The best way to update an existing pull request is to use an automation tool that reads the current git state and determines PR existence before deciding whether to create a new PR or update the existing one.

Does this PR automation work for CI-driven code reviews?▼

Yes, this PR automation works for CI-driven code reviews. It is designed for repository maintenance and feature development, allowing you to open a PR against main and automatically watch CI results for quick iteration.

Why does my automated PR workflow fail to track upstream branch alignment?▼

Automated PR workflows may fail to track upstream branch alignment if the local git state is not properly synced or if the gh CLI lacks the necessary permissions to read the repository state and execute GraphQL mutations.