Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From openshift-developer
Create a pull request from the current branch for a Jira issue. Use when changes are committed and pushed and the user wants to open a PR linking back to a Jira issue.
How this skill is triggered — by the user, by Claude, or both
Slash command
/openshift-developer:create-prThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
openshift-developer:create-pr
openshift-developer:create-pr
/openshift-developer:create-pr <ISSUE_KEY> [--upstream <owner/repo>] [--head <fork-owner>:<branch>]
Creates a pull request from the current feature branch, linking it to a Jira issue. Reads the repo's PR template, inspects the commit log, and generates a well-structured PR title and body. Designed as the final step of the solve pipeline, after /jira:solve, code-review:pre-commit-review and address-review-precommit.
Parse arguments:
$1 — Jira issue key (required, e.g. OCPBUGS-1234)--upstream — target repository (default: infer from gh repo view --json nameWithOwner)--head — PR head ref in fork-owner:branch format (default: current branch)Determine the current branch:
BRANCH=$(git branch --show-current)
Discover remotes, then determine the base branch:
REMOTE=$(git remote | head -1)
BASE_BRANCH=$(git remote show "$REMOTE" | sed -n 's/.*HEAD branch: //p')
Fall back to main if detection fails.
Read the commit history for the PR:
git log "${BASE_BRANCH}..HEAD" --format="%h %s%n%n%b" --reverse
Read the PR template if it exists:
cat .github/PULL_REQUEST_TEMPLATE.md 2>/dev/null || true
Title: Must start with <ISSUE_KEY>: followed by a concise summary derived from the commits.
Body: Structure using the PR template if one exists. Include:
https://redhat.atlassian.net/browse/<ISSUE_KEY>Always review AI generated responses prior to use.
Generated with [Claude Code](https://claude.com/claude-code) via openshift-developer plugin
Build and run the gh pr create command:
gh pr create \
--repo <UPSTREAM> \
--head <HEAD_REF> \
--no-maintainer-edit \
--title '<ISSUE_KEY>: <summary>' \
--body '<body>'
--upstream was provided, use it as --repo.--head was provided, use it directly.--repo and --head (defaults to current repo context and current branch).Print the PR URL returned by gh pr create.
Create a PR for a Jira issue (simple):
/openshift-developer:create-pr CNTRLPLANE-1234
Create a PR targeting a specific upstream from a fork:
/openshift-developer:create-pr OCPBUGS-5678 --upstream openshift/hypershift --head hypershift-community:fix/OCPBUGS-5678
$1 — Jira issue key (required)--upstream — target repository in owner/repo format (optional)--head — PR head ref in fork-owner:branch format (optional)git remote or git branch -vv) before selecting onenpx claudepluginhub saschagrunert/ai-helpers --plugin openshift-developerGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
6plugins reuse this skill
First indexed Jul 11, 2026