メニュー
Create a Git commit with a Jira-prefixed message derived from the staged diff. Use when the user asks to commit, wants to commit changes, or invokes /commit.
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.
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","Glob","Grep","Read","Skill"] |
| argument-hint | [optional message hint] |
| description | Create a Git commit with a Jira-prefixed message derived from the staged diff. Use when the user asks to commit, wants to commit changes, or invokes /commit. |
| name | commit |
Compose a well-crafted Git commit for the current set of changes.
Before composing the commit, invoke the format-source skill to ensure all changes follow Liferay's coding standards (both the automatic formatter and the manual rules). After it completes, any edits the formatter applied are part of what gets committed.
git add <file1> <file2> .... Do not include the user's own changes.Never use git add -A or git add ..
When nothing is staged, unstaged, or untracked, inform the user that there is nothing to commit and stop.
The ticket ID follows the pattern LPD-12345, LCD-12345, LRCI-1234, and similar forms (uppercase letters, hyphen, digits). Resolve the ticket in this order:
Branch Name — extract the ticket from the current branch (e.g., branch LPD-83847 yields ticket LPD-83847).
Recent Commits — when the branch name lacks a ticket, scan the last five commit messages for a ticket prefix.
User Argument — when ${ARGUMENTS} supplies a ticket ID, prefer that value.
Fallback — when no ticket surfaces, prompt the user for one.
Read the diff, understand the actual behavior change, then compose the message.
Format: <TICKET> <Summary of behavior change>
LPD-12345 LPD-67890 Summary.Examples:
LCD-50509 Grant ArgoCD permission to the correct namespaceLPD-83357 Add validation to prevent folder changes for CMS object definitionsLPD-83630 Fix typoLPD-84627 Prevent dispatch trigger loss when the Analytics admin user is missingAdd a body only when the title alone does not fully convey the change. Omit the body for trivial edits such as typo fixes, simple renames, or single-line changes.
When a body is warranted:
When ${ARGUMENTS} carries a hint or description rather than a ticket ID, incorporate it into the message.
Present the proposed commit message to the user and request confirmation. Once they approve, create the commit:
COMMIT_MESSAGE=$(cat <<'EOF'
<title>
<body if applicable>
EOF
)
git commit --message "${COMMIT_MESSAGE}"
When the user requests changes, revise the message and reconfirm.
Run git status to confirm the commit succeeded, then display the result.