メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | create-pr |
| description | 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. |
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 oneGenerate a comprehensive manual testing guide from a Jira issue, GitHub PR URLs, or both. Use when the user wants test steps, a QE test plan, or a testing guide for code changes.
Create Jira issues — story, bug, epic, feature, initiative, task, or feature-request — with CNTRLPLANE, OCPBUGS, GCP, HyperShift, ARO, ROSA conventions and type-specific templates
Generate triage reports and post findings to Jira and Slack
Query and deduplicate open CVE vulnerability issues from OCPBUGS for Node team components
Check whether a Jira issue is well-groomed and ready for /jira:solve
Analyze and compare disruption across one or more Prow CI job runs by examining interval data, audit logs, pod logs, and CPU metrics