jira-issue-to-pr skillA
jira-issue-to-pr is agent-read markdown (skill) from openhands/extensions: This skill should be used when the user asks to "set up a Jira automation to create pull requests", "poll Jira for create-pr issues", "automatically create GitHub PRs from Jira tickets", "deploy a Jira issue-to-PR automation", "create a Jira to GitHub PR workflow", or mentions automating GitHub PR creation from a Jira label. Deploys a cron-based OpenHands automation that watches a Jira Cloud project for issues labeled with a configurable label (default: "create-pr") and spawns an agent conversat.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Jira → GitHub PR Automation Deploys a cron automation that polls a Jira Cloud instance for open issues carrying a configurable label and, for each new issue, starts an OpenHands agent conversation that clones the GitHub repository specified in the ticket body, creates a branch, implements or placeholders the requested change, and opens a pull request. Once the conversation starts, it also posts a comment on the Jira ticket: "I'm on it: <conversation URL>". ## How It Works 1. **Poll** - every N minutes, `POST /rest/api/3/search/jql` on the Jira Cloud instance to find open issues with the configured label. 2. **Deduplicate** - on the very first run the script records a `first_run_at` baseline timestamp in the KV store; any issue whose `updated` timestamp predates that baseline is skipped (no backfill blast on first deploy). Using `updated` rather than `created` means an old issue that has its label added after the automation is deployed will still be picked up. Subsequent runs filter by both `first_run_at` and a KV-backed set of already-processed issue keys. A `max_new_per_run` cap (default 5) limits conversations …
Read the whole file at its exact version.
How to install
mdr add openhands/extensions/jira-issue-to-pr@git:20260706.20e1b9fmdr add openhands/extensions/jira-issue-to-pr@sha256:e5c143d6c0256e7cPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ztdd5g7qta4dk7xi)
0 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10124 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
openhands/extensions · 150 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ztdd5g7qta4dk7xi GET https://markdownregistry.com/api/v1/resolve?ref=openhands/extensions/jira-issue-to-pr GET https://markdownregistry.com/api/v1/blob/e5c143d6c0256e7cc1786716d358534701154ff86ea26495c8fa5eacf168ce26
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.