菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| allowed-tools | ["Bash","Edit","Glob","Grep","Read","Write"] |
| argument-hint | [path to Markdown file] |
| description | 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. |
| name | markdown-format |
Apply Liferay Markdown conventions to the target file so its structure, casing, and prose are consistent and professional.
When ${ARGUMENTS} is a path to a Markdown file, format that file. When no path is supplied, ask the user which file to format.
Read the target file in full before making changes. Note the frontmatter, headings, code blocks, and any conventions already in use.
Apply all conventions defined in .claude/rules/markdown-style.md. Work through each category in order. Fix each category before moving to the next.
Reread the file after the pass and confirm every check still holds.
Summarize the changes, grouped by category (frontmatter, headings, prose, shell, lists).
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.
