ticket-to-code-change
100 / 100 · Low risk
Fine to try.
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.
What this skill can do
We found nothing in the files we read that matches our rules. That does not prove the skill is safe: see the limits of static scanning.
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'ticket-to-code-change' ] || [ -L ~/.agents/skills/'ticket-to-code-change' ]; then echo 'A skill folder named ticket-to-code-change already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/OpenHands/extensions' "$d" && git -C "$d" checkout --quiet 'b98ac0671a51cc91bab3609bf4d334c7c832dd98' -- 'skills/ticket-to-code-change' && mkdir -p ~/.agents/skills && cp -R "$d"/'skills/ticket-to-code-change' ~/.agents/skills/'ticket-to-code-change' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'ticket-to-code-change' ~/.claude/skills/'ticket-to-code-change' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
[](https://zalavijaysinh.github.io/skilltrust/repos/OpenHands/extensions/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-12 | b98ac06 | 100 |