一键在 Manus 中运行任何 Skill

commit

星标4

分支0

更新时间2026年4月28日 15:00

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 页面并帮你完成安装。

在 Manus 中运行

来源

dannielraposo

dannielraposo/liferay-portal

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Commit Changes

Compose a well-crafted Git commit for the current set of changes.

1. Format Source

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.

2. Gather Context

When Claude modified or created files during this conversation, commit only those files. Stage them explicitly by name with git add <file1> <file2> .... Do not include the user's own changes.
When Claude did not modify any files in this conversation, commit all changes. Stage modified and deleted files, but leave untracked files alone. When untracked files exist, ask the user whether to include them.

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.

3. Extract the Jira Ticket

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.

4. Compose the Commit Message

Read the diff, understand the actual behavior change, then compose the message.

Title

Format: <TICKET> <Summary of behavior change>

Lead with the Jira ticket ID.
Follow with a concise summary of the outcome — the problem resolved or the behavior changed, not the code itself.
Use sentence case (capitalize the first word only).
Omit a trailing period.
Keep the full line under 72 characters, including the ticket prefix.
When a companion Jira ticket also applies (e.g., a related subtask), append it after the first: LPD-12345 LPD-67890 Summary.

Examples:

LCD-50509 Grant ArgoCD permission to the correct namespace
LPD-83357 Add validation to prevent folder changes for CMS object definitions
LPD-83630 Fix typo
LPD-84627 Prevent dispatch trigger loss when the Analytics admin user is missing

Body

Add 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:

Separate it from the title with a blank line.
Explain why the change is needed — the problem, the prior behavior, or the motivation. Do not restate the code.
Do not wrap lines in the body.
Write plain prose rather than bullet points, matching the repository convention.

When ${ARGUMENTS} carries a hint or description rather than a ticket ID, incorporate it into the message.

5. Confirm and Commit

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.

6. Post-Commit

Run git status to confirm the commit succeeded, then display the result.

同仓库更多 Skills

同仓库

poshi-shrink

dannielraposo/liferay-portal

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.

2026-05-064

format-source

dannielraposo/liferay-portal

Format source files to align with Liferay's coding standards.

2026-05-024

start-work

dannielraposo/liferay-portal

Start work on a Jira ticket.

2026-05-024

worktree-setup

dannielraposo/liferay-portal

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.

2026-05-024

dannielraposo/liferay-portal

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.

2026-05-014

format-source-add-rule

dannielraposo/liferay-portal

Add a new rule to the format-source skill, derived from a Git commit.

2026-05-014

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

Commit Changes

Compose a well-crafted Git commit for the current set of changes.

1. Format Source

2. Gather Context

When Claude modified or created files during this conversation, commit only those files. Stage them explicitly by name with git add <file1> <file2> .... Do not include the user's own changes.
When Claude did not modify any files in this conversation, commit all changes. Stage modified and deleted files, but leave untracked files alone. When untracked files exist, ask the user whether to include them.

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.

3. Extract the Jira Ticket

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.

4. Compose the Commit Message

Read the diff, understand the actual behavior change, then compose the message.

Title

Format: <TICKET> <Summary of behavior change>

Lead with the Jira ticket ID.
Follow with a concise summary of the outcome — the problem resolved or the behavior changed, not the code itself.
Use sentence case (capitalize the first word only).
Omit a trailing period.
Keep the full line under 72 characters, including the ticket prefix.
When a companion Jira ticket also applies (e.g., a related subtask), append it after the first: LPD-12345 LPD-67890 Summary.

Examples:

LCD-50509 Grant ArgoCD permission to the correct namespace
LPD-83357 Add validation to prevent folder changes for CMS object definitions
LPD-83630 Fix typo
LPD-84627 Prevent dispatch trigger loss when the Analytics admin user is missing

Body

Add 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:

Separate it from the title with a blank line.
Explain why the change is needed — the problem, the prior behavior, or the motivation. Do not restate the code.
Do not wrap lines in the body.
Write plain prose rather than bullet points, matching the repository convention.

When ${ARGUMENTS} carries a hint or description rather than a ticket ID, incorporate it into the message.

5. Confirm and Commit

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.

6. Post-Commit

Run git status to confirm the commit succeeded, then display the result.