ticket-to-code-change
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.
ソース情報
- リポジトリ
- OpenHands/extensions
- ソースの最終更新活動
- 2026年10月12日 10:42
- 検出された SKILL.md の言語
- 英語
- スター
- 167
- フォーク
- 114
インストール方法
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
ソースファイルを確認
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
ファイルエクスプローラー
6 ファイルSKILL.md を表示中
SKILL.md
ソースの指示 · 読み取り専用プレビュー- name
- ticket-to-code-change
- description
- 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.
- triggers
- ["/ticket-to-code-change:setup"]
# 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.
4. 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.
5. Create the automation through the Automation backend's prompt-preset
endpoint. On OpenHands Cloud or Enterprise the backend is the `<HOST>` value
in your system prompt, authenticated with
`Authorization: Bearer $OPENHANDS_API_KEY`. On a local Agent Canvas it is the
Automation backend described in `<RUNTIME_SERVICES>`, authenticated with the
runtime-provided automation API key.
6. 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.
GitHubで見る