Menu
Start work on a Jira ticket.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Format source files to align with Liferay's coding standards.
Check that a PR is ready to be sent for review.
Create a GitHub PR for the current branch. Use when the user asks to create a PR, send a PR, or invokes /pr.
Create a Jira bug ticket in the LPD project through the REST API. Use when the user asks to create or file a Jira bug or LPD ticket.
Create a Jira task in the LPD project through the REST API. Use when the user asks to create a Jira task or LPD task ticket.
Migrate a Liferay Poshi .testcase file to its modern test layer (Playwright, Jest, JUnit unit, Java integration). Routes each test to the right layer, consolidates compatible tests at write time, and follows existing Playwright patterns from a configurable reference folder. Use when the user asks to migrate, port, or convert a Poshi .testcase to Playwright, Jest, or JUnit.
| argument-hint | <ticket-key-or-url> |
| description | Start work on a Jira ticket. |
| name | start-work |
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.