ticket-to-code-change SKILL.md skillA
ticket-to-code-change from openhands/extensions is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add openhands/extensions/ticket-to-code-change@git:20261012.737ff7aPins git:20261012.737ff7a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- openhands/extensions
- Path
skills/ticket-to-code-change/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261012.737ff7a, committed Oct 12, 2026
- First version recorded
- Aug 24, 2026
- Size
- 2,630 bytes
- Repository stars
- 179
- License
- MIT
Set up a ticket-to-code-change automation using Linear as the issue tracker and GitHub, GitLab, or Bitbucket as the source-control provider. The Jira templates are served by the jira-issue-to-pr skill instead. 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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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: 1. The issue tracker: Linear. Jira automations are set up with the `jira-issue-to-pr` skill instead, which ships a poller. 2. The source-control provider: GitHub, GitLab, or Bitbucket Cloud. 3. The project or team to watch and the label or workflow state that means "implementation ready". 4. How a ticket identifies its target repository and base branch. 5. The polling schedule or issue event to use. 6. The ticket state to set when work starts and when the change request opens. 7. Whether linked dependencies must be completed before dispatch. ## Setup workflow 1. Verify that both required integrations are connected and can read the selected project and repository. 2. Prefer an issue event trigger when the deployment can receive events; otherwise use cron polling with durable issue-ID deduplication. 3. Limit each run to a small configurable number of new tickets. On initial deployment, establish a baseline instead of dispatching the entire backlog. …
Read the whole file at its exact version.
How to install
mdr add openhands/extensions/ticket-to-code-change@sha256:7db317dea3729b1bThe line at the top of this page pins the label git:20261012.737ff7a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ceynqd6dvgtgtgwu)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 24, 2026 and Oct 12, 2026, about one every 24 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.737ff7a latest | 2026-10-12 | 737ff7a | 2,630 B | A | view · diff |
| git:20261002.6ffd7e1 | 2026-10-02 | 6ffd7e1 | 2,485 B | A | view · diff |
| git:20260824.967c7ec | 2026-08-24 | 967c7ec | 2,278 B | A | view |
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 (2630 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 · 179 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ceynqd6dvgtgtgwu GET https://markdownregistry.com/api/v1/resolve?ref=openhands/extensions/ticket-to-code-change GET https://markdownregistry.com/api/v1/blob/7db317dea3729b1b78c2801ee599d571d3464b3dea1a93a43b3af985108af92c
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.