القائمة
Start work on a Jira ticket.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Shrink a Liferay component's Poshi test suite by merging overlapping tests. Use when the user asks to reduce, merge, or clean up Poshi tests for a @component-name.
Format source files to align with Liferay's coding standards.
Use when creating a Git worktree for parallel Liferay development, setting up a worktree bundle after ant all, checking which ports a worktree uses, listing all worktrees and their status, or tearing down a worktree. Covers the full lifecycle from Git worktree add through cleanup.
Create a GitHub pull request for the current branch, transition the corresponding Jira ticket to review, and record the PR link on the ticket. Use when the user asks to create a PR, send a PR, or invokes /pr.
Add a new rule to the format-source skill, derived from a Git commit.
Format a Markdown file to match Liferay conventions — frontmatter order, Title Case headings, braced shell variables, long-form CLI flags, and professional prose. Use when the user asks to format, clean up, polish, or copy-edit a Markdown file destined for the Liferay repository.
| argument-hint | <ticket-key-or-url> |
| description | Start work on a Jira ticket. |
| name | start-work |
Prepare a Liferay ticket for development. Drive every Jira interaction through the Jira Cloud REST API at liferay.atlassian.net, authenticated with ${JIRA_API_USER} / ${JIRA_API_TOKEN}.
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 step 4. 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. If 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. When ${PWD} matches */liferay-portal-<name>, the session is running inside a Liferay worktree that already has branch <name> checked out — skip this step and invoke the worktree-setup skill (action new) instead to provision the bundle, ports, and database.
Enter plan mode and read the tickets (both parent and child) to make the plan.