rhdh-jira-link

Files (8)

• SKILL.md
• openai.yaml · agents/
• config.example.json
• raise-pr-integration.md · references/
• create-pr-mr.js · scripts/
• lib.js · scripts/
• link-pr-mr.js · scripts/
• lib.test.mjs · tests/

SKILL.md (first lines)

# 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:

Compose the reviewer-facing PR or MR title and body, then invoke
`/prose-editing` once on both in the **flavored** register. Preserve Jira keys,
closing syntax, headings, checklists, links, and the required `Assisted-By`
line. Pass the edited strings to `create-pr-mr.js`; it is a transport layer and
must not edit them. The structured Jira link comment created later is a protocol
payload and does not receive this prose pass.

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

## Test plan
- [ ] …
EOF
)"
```

1. `git push -u origin HEAD` (unless `--no-push`)
2. Detects GitHub vs GitLab from `origin`
3. Runs `gh pr create` or `glab mr create`
4. Runs `link-pr-mr.js link` (unless `--no-link`). Missing Jira auth is an
   error; pass `--no-link` to skip linking.
5. 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):

1. `JIRA_API_TOKEN` + `login`/`server` in `~/.config/.jira/.config.yml`, or
2. `.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 an
attribution trailer to the **PR/MR body** when missing — `Assisted-By: pi
(<model>, thinking: <level>)` when `PI_MODEL` / `PI_REASONING_LEVEL` identify the
harness, and nothing at all when they do not (never a guessed tool). It adds
nothing when the body already carries an `Assisted-By:`/`Generated-by:` line. 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) — the first
line is the PR/MR title (the same string as the Web link) linking to the URL:

```
[org/repo #123: fix: widget [main]](https://github.com/org/repo/pull/123)
```

or, for GitLab:

```
[rhdh-plugin-catalog #1003: fix: … [release-2.1]](https://gitlab.cee.redhat.com/rhidp/rhdh-plugin-catalog/-/merge_requests/1003)
```

When no title is known, the line falls back to `PR: <url>` / `MR: <url>`.

Then, when any defaults were newly set:

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

From redhat-developer/rhdh-skills, Apache-2.0.

More from redhat-developer/rhdh-skills