pulsar-create-pr

Create Apache Pulsar pull requests via GitHub CLI with semantic branches.

8|2|Updated Feb 2, 2021
One-click install
npx skills add https://github.com/lhotari/pulsar-contributor-toolbox --skill pulsar-create-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pulsar-create-pr
Source: https://github.com/lhotari/pulsar-contributor-toolbox/tree/main/claude-code/skills/pulsar-create-pr
Command: npx skills add https://github.com/lhotari/pulsar-contributor-toolbox --skill pulsar-create-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of pull requests to the Apache Pulsar repository, reducing manual steps and ensuring PRs follow a consistent workflow.

Core Features & Use Cases

  • Automated PR creation: generate a branch, push to your fork, and open a PR with the appropriate title and body.
  • GitHub CLI integration: uses gh to submit PRs, optionally assigning reviewers and linking to related issues.
  • Workflow consistency: enforces semantic branch naming, PR templates, and standardized metadata for easier review.

Quick Start

Switch to a new feature branch, push to your fork, and create a pull request using gh.

Frequently Asked Questions about pulsar-create-pr

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

FAQPage Schema
How do I automate pull request creation for the Apache Pulsar repository?

Automating pull request creation for the Apache Pulsar repository involves generating a semantic branch, pushing commits to your forked remote, and submitting the PR via the GitHub CLI. This workflow enforces standardized PR metadata and templates.

What's the best way to manage branch creation and pushing to a fork for open-source Pulsar contributions?

Managing branch creation and pushing to a fork for Pulsar contributions is best handled by using semantic branch prefixes and an automated push mechanism. This ensures your local commits are correctly pushed to your forked remote before opening a pull request.

Does the GitHub CLI support assigning reviewers when opening Pulsar pull requests?

Yes, the GitHub CLI supports assigning reviewers when opening Pulsar pull requests. The PR creation process can optionally include reviewer assignments and link related issues directly through the gh command integration.

How does semantic branch naming work for Apache Pulsar pull requests?

Semantic branch naming for Apache Pulsar pull requests works by applying standardized prefixes to your branch names. This enforces workflow consistency and makes the review process easier by categorizing the nature of the changes.

Can I enforce standardized PR description metadata when submitting Pulsar contributions via GitHub?

Yes, you can enforce standardized PR description metadata when submitting Pulsar contributions via GitHub. The automated PR submission process applies consistent templates and required metadata to ensure your pull request follows repository guidelines.

Why does my Pulsar PR workflow require pushing to a forked remote first?

Your Pulsar PR workflow requires pushing to a forked remote first because direct push access to the Apache Pulsar repository is restricted. Pushing to your personal fork allows the GitHub CLI to safely open a pull request from your fork to the main project.