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.
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.
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.
Record a later `pr-check` Results Summary on an existing GitHub pull request. The skill adds a marker that a webhook reads to apply the tested commit’s status and a matching PR label; it does not run checks or set either value itself.
Runs the pre-merge validations that apply to a pull request’s changed files, including relevant formatting, build, and other checks. It reports pass or fail results in a summary, while integration, Playwright, and Poshi tests are handled separately.
Create a GitHub pull request from the current branch, assemble its title and description from the branch’s commits, and connect it to the relevant Jira tickets. The workflow also runs the required PR check and records the new PR URL on each ticket.
Inspect Liferay Git worktrees to see each worktree’s HTTP port, running status, port offset, and database name. You can also request the full port table and database summary for one worktree. The skill reads configuration and process information without changing state.
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.
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.
Turn a convention found in a Git commit or pull request review comment into a reusable `pr-reviewer` rule. The skill checks existing rules for overlap, writes the rule in the project’s format, and tests that it catches the original violation without flagging the fix.
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.
Investigate one failing Liferay test from its Testray result, reproduce it locally, and trace likely changes behind the failure. When a fix is confirmed, the workflow can prepare a commit and pull request, while recording the outcome on Jira.
Selects integration, Playwright, and Poshi tests that are most likely to catch regressions from the current branch’s changes. It produces and runs a focused shell script designed to fit a 20-minute local test window.
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.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)