Adoption

Agent Skills are supported by leading AI development tools.

VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory

openshift-eng/create-pr

Name: create-pr
Author: openshift-eng

plugins/openshift-developer/skills/create-pr/SKILL.md

npx skillsauth add openshift-eng/ai-helpers create-pr

Clean

TrivyContainer and dependency vulnerability scanner

Clean

SemgrepStatic code analysis for vulnerabilities

Clean

mcp-scan (Snyk)Model Context Protocol security validation

Skipped

Snyk (dep)Open source security scanning

Skipped

Socket.devSupply chain security analysis

Skipped

VirusTotalMulti-engine malware detection

Skipped

CrowdStrikeAdvanced threat intelligence

Skipped

OSV-ScannerOpen Source Vulnerability database check

Skipped

OWASP Dep-Check

Name

openshift-developer:create-pr

Synopsis

/openshift-developer:create-pr <ISSUE_KEY> [--upstream <owner/repo>] [--head <fork-owner>:<branch>]

Description

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.

Implementation

Step 1: Gather context

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

Step 2: Compose the PR

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:
- A description of the changes based on the commit log
- A link to the Jira issue: https://redhat.atlassian.net/browse/<ISSUE_KEY>
- The following footer at the very end:
```
Always review AI generated responses prior to use.
Generated with [Claude Code](https://claude.com/claude-code) via openshift-developer plugin
```

Step 3: Create the PR

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>'

If --upstream was provided, use it as --repo.
If --head was provided, use it directly.
If neither was provided, omit --repo and --head (defaults to current repo context and current branch).

Step 4: Report

Print the PR URL returned by gh pr create.

Return Value

PR URL: the URL of the newly created pull request

Examples

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

Arguments

$1 — Jira issue key (required)
--upstream — target repository in owner/repo format (optional)
--head — PR head ref in fork-owner:branch format (optional)

Guidelines

Discover remotes first (e.g. git remote or git branch -vv) before selecting one
Always include the Jira issue key prefix in the PR title
Always include the AI-generated footer at the end of the PR body
Use the repo's PR template when available
Derive the PR description from the actual commit log, not from assumptions

openshift-eng/create-pr

plugins/openshift-developer/skills/create-pr/SKILL.md

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.

105 stars

tools

Updated Jun 25, 2026

$ install --global

skillsauth

npx skillsauth add openshift-eng/ai-helpers create-pr

Install this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.

Security Scan Results

3 of 9 scanners reported clean

Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.

Scanners Passed

Scanners in report

Clean

TrivyContainer and dependency vulnerability scanner

95%

Clean

SemgrepStatic code analysis for vulnerabilities

95%

Clean

mcp-scan (Snyk)Model Context Protocol security validation

95%

Skipped

Snyk (dep)Open source security scanning

50%

Skipped

Socket.devSupply chain security analysis

50%

Skipped

VirusTotalMulti-engine malware detection

50%

Skipped

CrowdStrikeAdvanced threat intelligence

50%

Skipped

OSV-ScannerOpen Source Vulnerability database check

50%

Skipped

OWASP Dep-Check

50%

Last scanned: Jun 25, 2026, 6:29 AM54.2s1 file scanned

SKILL.md

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.

Name

openshift-developer:create-pr

Synopsis

/openshift-developer:create-pr <ISSUE_KEY> [--upstream <owner/repo>] [--head <fork-owner>:<branch>]

Description

Implementation

Step 1: Gather context

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

Step 2: Compose the PR

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:
- A description of the changes based on the commit log
- A link to the Jira issue: https://redhat.atlassian.net/browse/<ISSUE_KEY>
- The following footer at the very end:
```
Always review AI generated responses prior to use.
Generated with [Claude Code](https://claude.com/claude-code) via openshift-developer plugin
```

Step 3: Create the PR

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>'

If --upstream was provided, use it as --repo.
If --head was provided, use it directly.
If neither was provided, omit --repo and --head (defaults to current repo context and current branch).

Step 4: Report

Print the PR URL returned by gh pr create.

Return Value

PR URL: the URL of the newly created pull request

Examples

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

Arguments

$1 — Jira issue key (required)
--upstream — target repository in owner/repo format (optional)
--head — PR head ref in fork-owner:branch format (optional)

Guidelines

Discover remotes first (e.g. git remote or git branch -vv) before selecting one
Always include the Jira issue key prefix in the PR title
Always include the AI-generated footer at the end of the PR body
Use the repo's PR template when available
Derive the PR description from the actual commit log, not from assumptions

Related Skills

openshift-eng/jira-solve

tools

VerifiedTrustedCommunity

Analyze a JIRA issue and create a pull request to solve it. Use when the user wants to implement a fix or feature described in a Jira issue, push a branch, and open a draft PR.

112SKILL.mdUpdated Jul 29, 2026

openshift-eng/jira-solve

openshift-eng/deep-review

development

VerifiedTrustedCommunity

Use when a deeper level of code review is requested. Multi-agent panel code review with specialist reviewers and forced runtime reproducers for all BLOCKING bug findings. Optionally posts to GitHub/GitLab as a PENDING review.

112SKILL.mdUpdated Jul 29, 2026

openshift-eng/deep-review

openshift-eng/review-docs

development

VerifiedTrustedCommunity

Review agentic documentation — verify claims locally against source code first, then use chai-bot for cross-repo and cross-functional verification

112SKILL.mdUpdated Jul 10, 2026

openshift-eng/review-docs

openshift-eng/prow-job-analysis

development

VerifiedTrustedCommunity

Use this skill when debugging a failed Prow CI job.

112SKILL.mdUpdated Jul 9, 2026

openshift-eng/prow-job-analysis

Download

For Claude Desktop. Download once, then upload the file in the app — no terminal needed.

Need help? View full Cowork setup guide →

Install manually

Choose your platform

# Clone the repo
git clone https://github.com/openshift-eng/ai-helpers.git

# Copy into Claude Code skills folder (global)
cp -r ai-helpers/plugins/openshift-developer/skills/create-pr ~/.claude/skills/

Claude Code Skills — official skills path docs.

Repository

openshift-eng/ai-helpers

105 stars

Compatible with

Claude Code

OpenAI Codex CLI

ChatGPT