Menú
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.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional 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.
Start work on a Jira ticket.
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.
| allowed-tools | Bash(curl *), Bash(git *), Glob, Grep, Read |
| argument-hint | [commit hash or description] |
| description | 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. |
| name | jira-bug |
Create a bug ticket in the LPD Jira project through the REST API, authenticating with credentials from the ${JIRA_API_USER} and ${JIRA_API_TOKEN} environment variables.
When ${ARGUMENTS} is a commit hash, inspect the commit with git show to understand the fix and infer the bug it addresses. When ${ARGUMENTS} is a free-form description, use it directly.
Request any missing details from the user:
The LPD project requires the following fields. Apply these defaults unless the user specifies otherwise:
Master (ID: 16660).Content Publishing > Resource Importer (ID: 15805)Data Integration > Export/Import (ID: 16131)Headless Batch Engine API (ID: 16022)customfield_10979): None (ID: 14468).When no listed component matches, search by keyword:
curl \
--silent \
--url "https://liferay.atlassian.net/rest/api/3/project/LPD/components" \
--user "${JIRA_API_USER}:${JIRA_API_TOKEN}" \
| python3 -c "import json, sys; [print(f'{c[\"id\"]:>6} {c[\"name\"]}') for c in json.load(sys.stdin) if 'SEARCH_TERM' in c['name'].lower()]"
Submit the issue through Jira REST API v3:
curl \
--data '<JSON payload>' \
--header "Content-Type: application/json" \
--request POST \
--silent \
--url "https://liferay.atlassian.net/rest/api/3/issue" \
--user "${JIRA_API_USER}:${JIRA_API_TOKEN}"
Author the description in Atlassian Document Format (ADF) with the following sections, in order: Description, Steps to Reproduce, Expected Behavior, Actual Behavior. Append a Fix section when a commit is referenced.
Return the ticket key and the browse URL: https://liferay.atlassian.net/browse/<KEY>.