ticket-to-code-change

Set up a ticket-to-code-change automation using Jira or Linear as the issue tracker and GitHub, GitLab, or Bitbucket as the source-control provider. Watches for implementation-ready tickets, starts an OpenHands conversation to implement and test the request, opens a pull or merge request, and links the result back to the ticket.

Jump to install

Repository: OpenHands/extensions
Last source activity: August 24, 2026 at 16:58
Detected SKILL.md language: English
Stars: 136
Forks: 79

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/OpenHands/extensions --skill ticket-to-code-change

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

6 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

github-pr-reviewer

Create an automation that reviews GitHub pull requests when a configurable trigger label is applied. Polls one or more repositories deterministically, starts one OpenHands review conversation per label event with the pull request's head commit already checked out, and publishes the review to GitHub.

2026-08-23

news-digest

Create an automation that reads a list of public RSS and Atom feeds on a schedule - daily by default - keeps what is new and matches the configured topics, and has an agent write a short digest of it. It needs no credentials: the feeds are public URLs and the conversation is started with no secrets and no MCP servers.

2026-08-20

github-agents-md-maintainer

Create an automation that keeps AGENTS.md current in one or more GitHub repositories. On a schedule - weekly by default - it clones the default branch, starts an OpenHands conversation that reads the repository and creates or updates AGENTS.md, and opens a pull request with the result.

2026-08-20

View all from this repository

Ticket to code change

Create an automation that turns implementation-ready tickets into tested pull requests or merge requests.

Information to collect

Ask the user for:

The issue tracker: Jira Cloud or Linear.

The source-control provider: GitHub, GitLab, or Bitbucket Cloud.

The project or team to watch and the label or workflow state that means "implementation ready".

How a ticket identifies its target repository and base branch.

The polling schedule or issue event to use.

The ticket state to set when work starts and when the change request opens.

Whether linked dependencies must be completed before dispatch.

Setup workflow

Verify that both required integrations are connected and can read the selected project and repository.

Prefer an issue event trigger when the deployment can receive events; otherwise use cron polling with durable issue-ID deduplication.

Limit each run to a small configurable number of new tickets. On initial deployment, establish a baseline instead of dispatching the entire backlog.

Build a prompt that includes the full ticket, acceptance criteria, dependency status, repository, base branch, and provider-specific request terminology. Require the agent to run the repository's tests before opening the pull request or merge request.

Create the automation through the Automation backend described in <RUNTIME_SERVICES>. Use its prompt-preset endpoint and authenticate with the runtime-provided automation API key.

Configure the automation to post the OpenHands conversation URL immediately and the resulting pull-request or merge-request URL back to the ticket.

Do not dispatch tickets with unresolved dependencies or without an unambiguous target repository; comment on the ticket with the missing information instead.