Jira PR / MR links

Zero-token Node scripts for GitHub and GitLab: create the PR/MR, attach a Jira remote Web link, post or update a structured comment, and optionally fill empty issue fields.

Scripts live under this skill's

scripts/

directory. Resolve that path from the installed skill root (agents already have it when reading this file):

bash

SKILL="$(cd "$(dirname "$0")" && pwd)"   # or the absolute path to this skill root
node "$SKILL/scripts/create-pr-mr.js" …
node "$SKILL/scripts/link-pr-mr.js" …

Another skill that needs the link step invokes

/rhdh-jira-link

by name and lets this skill run its own scripts; it never calls into this directory by path.

Preferred: one-shot create (

create-pr-mr.js

)

After the feature branch is committed:

bash

node "$SKILL/scripts/create-pr-mr.js" \
  --issue RHIDP-12345 \
  --title 'fix: short summary' \
  --target main \
  --body "$(cat <<'EOF'
## Summary
- …

## Test plan
- [ ] …

Generated-by: cursor
EOF
)"

```
git push -u origin HEAD
```
(unless
```
--no-push
```
)
Detects GitHub vs GitLab from
```
origin
```
Runs
```
gh pr create
```
or
```
glab mr create
```
Runs
```
link-pr-mr.js link
```
(unless
```
--no-link
```
). Missing Jira auth is an error; pass
```
--no-link
```
to skip linking.
Opens the diffs page (unless
```
--no-open
```
)

Flags:

--draft

--no-push

--no-link

--no-open

--no-defaults

--no-comment

--no-jira-ref

--host github|gitlab

Auth

Either works (same token either way):

JIRA_API_TOKEN

login

server

~/.config/.jira/.config.yml

, or

```
.jira-token
```
(
```
email:token
```
) next to
```
acli
```
— the same credential
```
/rhdh-jira-api
```
uses. Invoke
```
/rhdh-jira-api
```
by name for the authoritative auth setup instead of duplicating it here.

create-pr-mr.js

appends

Ref: https://redhat.atlassian.net/browse/KEY

and

Generated-by: cursor

to the PR/MR body when missing. It skips the Jira

Ref:

line for

community-plugins

remotes (or when

--no-jira-ref

is set) so that repo stays free of Jira browse URLs in git history / PR text.

Link-only:

link-pr-mr.js

When a PR/MR already exists:

bash

node "$SKILL/scripts/link-pr-mr.js" link \
  --issue RHIDP-12345 \
  --url 'https://gitlab.cee.redhat.com/rhidp/example/-/merge_requests/817' \
  --title 'example #817: fix: short summary' \
  --host gitlab

```
--host
```
optional; inferred from URL when omitted.
```
--no-defaults
```
skips In Progress + metadata fills (Web link + comment still run).
```
--no-comment
```
skips the Jira comment.
If a comment already mentions the PR/MR URL, it is updated in place (comments are paginated).

RHDHPLAN → RHIDP auto-move

If the linked issue is an Epic, Story, or Task in RHDHPLAN,

link

moves it to RHIDP (same issue type) via the Jira bulk-move API, then continues Web link / defaults / comment on the new key. Features and other RHDHPLAN types are left alone.

Stdout includes

move: …

and the post-move

issue:

key.

Comment shape (only newly set fields; omit

kept

values):

PR/MR:
* example #817: fix: short summary

Adjusted fields:
* Priority: Normal
* Status: In Progress

Visible link text matches the Web link title (

repo #N: <title>

Mark merged

bash

node "$SKILL/scripts/link-pr-mr.js" mark-merged --issue RHIDP-12345

Prefixes Web link titles with

[x] merged:

. Does not re-apply defaults/comment. Stdout lists each title and its PR/MR URL (indented under the title).

mark-merged

checks merge status via

gh

glab

. Failed checks print a

warn:

line. For GitLab remotelinks it passes

--hostname

from the URL (e.g.

gitlab.cee.redhat.com

), so CEE MRs resolve against the right host. Prefer

glab

default

host: gitlab.cee.redhat.com

~/.config/glab-cli/config.yml

for day-to-day CEE work.

When summarizing to the user, use markdown links (

[<title>](<url>)

Title format (for

link --title

)

<repo-short-name> #<id>: <full PR/MR title>

Merged:

[x] merged: <repo-short-name> #<id>: <full PR/MR title>

Defaults

link

applies (only if empty)

No built-in team/assignee values. First run with defaults enabled requires a config file (or env/CLI). Missing keys error when applying defaults; the Web link and comment still succeed with

--no-defaults

bash

mkdir -p ~/.config/rhdh-jira-link
cp "$SKILL/config.example.json" ~/.config/rhdh-jira-link/config.json
# edit assigneeEmail, teamId, teamName, boardId, …

Also accepted:

$JIRA_PR_MR_CONFIG

$SKILL/config.local.json

(keep personal email out of the repo).

Precedence: CLI > env > config file > Jira CLI hints (

login

board.id

from

~/.config/.jira/.config.yml

may fill assignee/board only).

Field	Required when applying defaults
`assigneeEmail`	yes (or Jira `login` email)
`teamId` / `teamName`	yes, or set either to `NONE` to skip team and sprint
`boardId`	yes (or jira CLI `board.id` ), unless team/sprint skipped via `NONE`
`storyPoints`	yes
`priorityName`	yes (only fills when priority is empty)
`storyPointsField`	yes
`teamField` / `sprintField`	yes, unless team/sprint skipped via `NONE`
Status	→ In Progress unless already In Progress / Review / Closed

Skip all defaults:

--no-defaults

JIRA_PR_MR_APPLY_DEFAULTS=0

Skip only team + sprint (still set points / assignee / priority / In Progress):

json

"teamName": "NONE",
"teamId": "NONE"

Relationship to

/rhdh-pr-create

/rhdh-pr-create

owns the rhdh-plugins / community-plugins monorepo PR flow (build, changesets, recordings). This skill owns the Jira Web link + comment (and optional defaults) for any repo. Invoke it by name; do not read or run its files.

Once

/rhdh-pr-create

has created a PR, it hands the URL and title back and this skill runs the link step with

--no-defaults

, leaving

/rhdh-pr-create

free to transition the issue to Review (see references/raise-pr-integration.md).

Agent checklist

Resolve Jira key. Ask if missing (unless user skipped Jira).
Commit on a feature branch. Put the Jira browse URL and
```
Generated-by: cursor
```
in the PR/MR body (
```
create-pr-mr.js
```
appends them when missing; skips
```
Ref:
```
for community-plugins).

Run create-pr-mr.js
once. Report

url:

diffs:

browserOpened:

jiraLink:

from its stdout (

browserOpened: true

--no-open

means the open step is already done).

Fallback: raw create → run
```
link-pr-mr.js
```
, then open diffs yourself once.
For mark-merged:
```
link-pr-mr.js mark-merged --issue KEY
```
.
In user-facing summaries, link PR/MRs as
```
[<title>](<url>)
```
.

Every run here is an external write

Creating a PR/MR, writing a Jira Web link, posting a comment, moving an issue to another project, and filling default fields all change something outside the session. Invoke

/mutation-gate

and follow it before the first command: one script invocation can perform several of these at once, so state them as one set — push, create, link, comment, defaults — and get a single approval covering all of them.

Completion

Complete when the answer names the PR/MR URL and diffs link, the Jira key it was linked to — including the post-move key when an RHDHPLAN Epic, Story, or Task moved to RHIDP — the Web link title, whether the comment was posted or updated, which default fields were newly set, and every

warn:

line the scripts printed. Report the fields the script left alone as kept, never as set. A Web link that succeeded followed by a defaults update that errored is a partial link, so say which half landed.

rhdh-jira-link

NPX Install

Tags

SKILL.md Content

Jira PR / MR links

Preferred: one-shot create (
`create-pr-mr.js`
)

Auth

Link-only:
`link-pr-mr.js`

RHDHPLAN → RHIDP auto-move

Mark merged

Title format (for
`link --title`
)

Defaults
`link`
applies (only if empty)

Relationship to
`/rhdh-pr-create`

Agent checklist

Every run here is an external write

Completion

rhdh-jira-link

NPX Install

Tags

SKILL.md Content

Jira PR / MR links

Preferred: one-shot create (create-pr-mr.js)

Auth

Link-only: link-pr-mr.js

RHDHPLAN → RHIDP auto-move

Mark merged

Title format (for link --title)

Defaults link applies (only if empty)

Relationship to /rhdh-pr-create

Agent checklist

Every run here is an external write

Completion

Preferred: one-shot create (
`create-pr-mr.js`
)

Link-only:
`link-pr-mr.js`

Title format (for
`link --title`
)

Defaults
`link`
applies (only if empty)

Relationship to
`/rhdh-pr-create`