eventaservo-pr-creator

Open or update GitHub pull requests via the GitHub CLI.

31|8|Updated Oct 11, 2018
One-click install
npx skills add https://github.com/eventaservo/eventaservo --skill eventaservo-pr-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eventaservo-pr-creator
Source: https://github.com/eventaservo/eventaservo/tree/main/.agents/skills/eventaservo-pr-creator
Command: npx skills add https://github.com/eventaservo/eventaservo --skill eventaservo-pr-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the Open/Update PR workflow for the Eventaservo repository by using the GitHub CLI, eliminating manual PR paperwork and ensuring consistency with project conventions.

Core Features & Use Cases

  • Open new pull requests on a feature branch with conventional, English PR text and summaries.
  • Update existing pull requests by editing the title and body via gh pr edit to reflect changes.
  • Enforce guardrails: require explicit user consent before pushing or modifying remote PR state and follow AGENTS.md guidelines.

Quick Start

Ask me to open or update a PR for the current branch using gh.

Frequently Asked Questions about eventaservo-pr-creator

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

FAQPage Schema
How do I open a GitHub pull request using gh CLI from the command line?

Opening a GitHub pull request with gh CLI involves initiating the command on a feature branch, which then guides you through creating conventional, English PR text and summaries aligned with project conventions.

Can I update an existing pull request title and body with gh CLI?

Yes, you can update an existing pull request title and body using the gh pr edit command, allowing you to modify the PR state to accurately reflect recent changes made to the branch.

Do I need explicit consent before pushing changes to a remote GitHub PR?

Yes, explicit user consent is strictly required before pushing or modifying the remote pull request state, ensuring guardrails are enforced and preventing unauthorized updates to the GitHub repository.

What prerequisites are needed to automate PR workflows with GitHub CLI?

Automating PR workflows requires a locally configured git workflow, a valid gh authentication setup, and adherence to AGENTS.md conventions to ensure proper pull request message formatting and repository access.

Does automating pull requests with gh CLI enforce project conventions?

Yes, automating pull requests with gh CLI enforces project conventions by aligning PR descriptions and titles with established AGENTS.md guidelines, ensuring consistency across the repository without manual formatting.

Why use gh CLI over manual PR creation for repository workflows?

Using gh CLI eliminates manual PR paperwork and ensures consistency with project conventions, streamlining the workflow by automating the generation of conventional text and summaries for GitHub pull requests.