Prepares a Jira bug, story, or task for development by assigning it, applying the appropriate workflow transitions, and handling its Technical Task subtask when applicable. It creates or checks out a branch named for the target ticket and drafts a plan from the parent and child tickets.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Start work on a Jira ticket.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Prepare a Liferay ticket for development.
Accept a key (LPD-86295) or a browse URL from ${ARGUMENTS}. When nothing is supplied and ${PWD} matches */liferay-portal-<KEY> where <KEY> matches the Jira pattern [A-Z]+-[0-9]+, derive the key from the directory name. Otherwise, ask the user.
Abort when the working tree has uncommitted changes.
Fetch the ticket (issue type, current assignee, subtasks) and resolve the target — the ticket where the branch and active work state live:
10004) — the bug itself. There is no child.10001) or Task (10002) — the Technical Task (10153) subtask. Jira autocreates it when the parent is moved to an in-progress status, so the target does not exist yet and must be resolved after Start Work on the Parent. It may exist from a previous attempt, in which case it becomes the target.Assign the parent to the user and apply the transitions below. When the parent is already in an in-progress status by a different user, refuse to continue.
| Parent Type | Destination | Transition IDs |
|---|---|---|
| Bug | In Progress | 61 |
| Story | In Development | 41, then 61 |
| Task | In Progress | 21 |
For a Story, apply the two transitions in sequence: 41 moves it to Ready for Development, which triggers Jira to autocreate the Technical Task subtask, then 61 moves it to In Development.
Skip for Bug. For Story / Task, refetch the parent's subtasks until the Technical Task appears, then assign it to the user and transition it:
| Child Type | Destination | Transition ID |
|---|---|---|
| Technical Task | In Progress | 41 |
Branch off the current HEAD, named after the target key. When the branch already exists, check it out instead.
Enter plan mode and read the tickets (both parent and child) to make the plan.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Use this skill to format Liferay source files according to the project’s conventions. It describes the formatter workflows for modules and committed changes, how to handle Go and shell files, and which generated files to leave untouched.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use this skill to file a bug in the LPD Jira project from a description or fix commit. It gathers reproduction steps and expected versus actual behavior, applies required project fields, and returns the created ticket key and link.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use this skill to create a Task ticket in the LPD Jira project from a description or commit. It gathers missing details, selects a matching component, formats the description with acceptance criteria when applicable, and returns the ticket key and link.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Format Markdown files for Liferay repositories by aligning front matter, heading capitalization, shell examples, and prose with the project’s style rules. Use it to clean up or copy-edit a document and receive a summary of the changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Analyzes a Liferay Poshi `.testcase`, checks feasibility and existing coverage, then routes each test to Playwright, Jest, JUnit unit, or Java integration tests. It creates a migration plan and can implement the approved changes using repository patterns.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan and carry out a reduction of a Liferay component’s Poshi test suite by identifying overlapping tests and combining their unique assertions. The skill inventories matching test files, preserves tests with special setup or properties, and commits each planned rename or merge separately.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.