liferay/liferay-portal

Creates a pull request for the current branch, ensuring tests are added, running pre-checks, and linking and transitioning Jira tickets. Use when submitting code for review.

Automatically format Java, JavaScript, and other source files to comply with Liferay's coding standards using built-in formatters and manual rules.

Encode a formatting convention spotted in a Git commit into a reusable rule for the format-source skill. Use this to systematically add formatting rules for Java, properties, XML, and more.

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.

Creates a Jira task in the LPD project via REST API, inferring details from commit hashes or descriptions. Use when you need to create a Jira task or LPD ticket.

Provides guidance on building and customizing themes and visual designs for Liferay Portal, including CSS, templates, and frontend assets.

Set up and troubleshoot Liferay MCP server, including CLI restart ordering, connection issues, and error diagnosis. Use when enabling MCP or handling tool call errors.

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.

Automatically runs premerge checks on a PR branch, including builds, unit tests, and source formatting, to ensure code readiness before review.

Posts a pr-check run summary as a comment on an existing GitHub pull request with a hidden marker for a webhook to update commit status and labels. Use after rerunning pr-check on an open PR.

Migrates Liferay Poshi test cases to appropriate modern frameworks (Playwright, Jest, JUnit). Automatically classifies tests, consolidates compatible ones, and follows existing patterns.

Shrink a Liferay component's Poshi test suite by merging overlapping tests, reducing test count while maintaining coverage. Ideal when asked to reduce, merge, or clean up Poshi tests.

Prepares a Liferay ticket for development by assigning it, transitioning its status in Jira, creating a Git branch, and opening a planning session.

Resolves a single Liferay test failure end-to-end by fetching failure data from Testray, determining the root cause, and opening a pull request with the fix or reporting the outcome.

Generates a runnable shell script (under 20 minutes) that executes the tests most likely to regress for the current branch, covering unit, integration, Playwright, and Poshi tests. Use before merging to catch regressions without running the full suite.

Lists all Git worktrees in a Liferay repository showing HTTP ports, running status, offsets, and database names. Also provides detailed port configuration and database info for a single worktree.