raise-pr

Create pull requests from a Git branch with pre-commit checks.

71|88|Updated Nov 8, 2023
One-click install
npx skills add https://github.com/openshift/lightspeed-service --skill raise-pr-openshift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: raise-pr
Source: https://github.com/openshift/lightspeed-service/tree/main/.cursor/skills/raise-pr
Command: npx skills add https://github.com/openshift/lightspeed-service --skill raise-pr-openshift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the routine process of creating a pull request from a feature branch, ensuring code changes are proposed consistently and with the right checks.

Core Features & Use Cases

  • Branch-aware PR creation from the current working branch with a standardized title and description
  • Integration of pre-commit checks and tests to prevent broken changes from being proposed
  • Use Case: A developer finishes a feature on a branch and wants to open a PR with reviewers requested and a clean change summary

Quick Start

Run the PR workflow to create a new pull request from your current branch after pre-commit checks pass.

Frequently Asked Questions about raise-pr

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

FAQPage Schema
How do I automate pull request creation from a git branch?

Automating pull request creation from a git branch involves coordinating with the GitHub CLI to generate a standardized title and description from your current working branch, streamlining the proposal process.

What's the best way to run pre-commit checks before opening a GitHub PR?

Running pre-commit checks before opening a GitHub PR is handled by integrating tests directly into the PR workflow, preventing broken changes from being proposed and ensuring code consistency.

Does this PR workflow support selecting the correct base branch automatically?

This PR workflow supports selecting the correct base branch automatically by coordinating with git and repository conventions, applying safeguards to ensure changes merge into the intended target.

When do I need to use an automated pull request workflow in git?

You need to use an automated pull request workflow in git when you finish a feature on a branch and want to open a PR with reviewers requested and a clean change summary consistently.

How does the pull request generator handle existing PRs on the same branch?

The pull request generator handles existing PRs on the same branch by applying safeguards that prevent duplicate proposals, coordinating with repository conventions to update or bypass existing requests.