rhdh-pr-mr

Files (4)

• SKILL.md
• openai.yaml · agents/
• create-pr-mr.sh · scripts/
• smoke.sh · tests/

SKILL.md (first lines)

# RHDH PR / MR opener

Shared script for push + open. Caller owns the commit and `/mutation-gate`
approval when an agent is driving. Weekly bots may call the script unattended.

## Boundaries

- **Not** `/rhdh-pr-create` (plugin changesets, recordings, monorepo publish).
- **Requires** a known Jira key and calls `/rhdh-jira-link` after opening. Stop
  before pushing when no issue is known; never invent one.
- **Requires** an attribution trailer on the commit and in the description. The
  payload is open: name the tool, then add only the agent, model, provider and
  thinking level that are actually known.
- Midstream `createPR.sh` (distgit) stays for `updateBaseImages.sh` until a later migration.

## Script

```bash
SKILL=<this skill's directory>
"$SKILL/scripts/create-pr-mr.sh" \
  --cwd /path/to/checkout \
  --base main \
  --head chore/my-topic \
  --title 'chore: short summary' \
  --body-file /tmp/body.md \
  --issue RHIDP-12345 \
  --attribution '<tool> (<agent> + <model> (<provider>), thinking: <level>)' \
  [--label ok-to-test] \
  [--dry-run]
```

Default is `--no-open` (no browser). Pass `--open` only for interactive agent runs.
`GITLAB_PIPELINE=true` forces no browser.

The script appends ` [<base>]` to `--title` when that suffix is missing, including
for `main` (`chore: short summary` becomes `chore: short summary [main]`). A
title that already ends with the base branch is left as-is.

Resolve the `--attribution` value from the current work, filling in whatever is
known and stopping there:

| Known | Value |
| --- | --- |
| tool + agent + model + provider + thinking | `paseo (pi + DeepSeek V4.1 Flash (EnMaaS), thinking: off)` |
| tool + model + thinking | `pi (GLM 5.3, thinking: high)` |
| tool only | `pi` |

- **Tool** is where the agent ran: `paseo`, `pi`, `cursor`, a CI bot script.
- **Agent, provider, thinking level** are optional and go in that order;
  `thinking:` is a labelled field, not a third model word.
- **Never guess and never emit a placeholder.** A missing model is dropped, not
  filled with a stand-in string that the next agent will copy verbatim. No
  `Unknown AI`, no invented version numbers, no borrowed IDE name.
- If `--attribution` is omitted, the script falls back to `PI_MODEL` and
  `PI_REASONING_LEVEL` (`pi (<model>, thinking: <level>)`) before failing.
- The trailer key written is `Assisted-By:`; `Generated-by:` is accepted on read,
  so older callers and existing commits keep working. A value that already starts
  with either key is used verbatim.
- `--assisted-by` and `RHDH_ASSISTED_BY` remain accepted as aliases of
  `--attribution` and `RHDH_ATTRIBUTION`.

Before pushing, the script verifies that the latest commit carries an attribution
trailer. Any payload satisfies it — the commit trailer and the `--attribution`
value do not have to match, so a caller can pass less detail than the commit has.
The script adds the resolved line (when the description has none) and
`Related Jira: [KEY](https://redhat.atlassian.net/browse/KEY)` to the PR/MR
description.

GitLab MRs set `remove_source_branch: true` so merging deletes the topic branch.

Stdout includes `url: …`. Exit 0 if a PR/MR already exists for `--head`.

## Jira

| Condition | Behavior |
| --- | --- |
| `--issue KEY` or `JIRA_ISSUE` set + `JIRA_API_TOKEN` | Add the linked issue to the description, then invoke `/rhdh-jira-link` (`link-pr-mr.js link`). The Jira comment links the PR/MR title (`repo #id: title [base]`) to the URL (plus optional Adjusted fields). |
| Issue set but no token / missing link script | The linked description remains; warn that the Jira backlink was skipped. |

Override the link scripts directory with `RHDH_JIRA_LINK_SCRIPTS` when the
sibling skill is not next to this one in the pack checkout.

## Agents

1. Resolve the most specific available attribution from the table above — fill
   in what you know, stop at the tool name — and add that `Assisted-By:`
   trailer to the commit.
2. Resolve the Jira key from the conversation. Stop before pushing when none is
   known; never turn a plain issue key in the description into an unlinked label.
3. Follow `/mutation-gate` for push + open + Jira link.
4. Invoke `/rhdh-pr-mr` by name (or run the script path when already inside a
   skill clone), passing `--issue` and `--attribution`.
5. Report the `url:` line.

## Tests

```bash
bash -n "$SKILL/scripts/create-pr-mr.sh"
shellcheck --severity=warning "$SKILL/scripts/create-pr-mr.sh"
"$SKILL/scripts/create-pr-mr.sh" --help
"$SKILL/tests/smoke.sh"
```

## Completion

Done when the topic branch is pushed; the latest commit and PR/MR description
carry an attribution trailer whose payload names every part that was actually
known; the description contains the Markdown Jira link; a Jira Web link was
updated or its missing credential was reported; and a GitLab MR is configured to
delete its source branch after merge.

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

More from redhat-developer/rhdh-skills