commit-confirm

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Commit Confirm

Use this wrapper only after the explicit opt-in described in the frontmatter. A normal approval-first commit request does not opt in to this skill or its whole-working-tree default.

Use this skill to run

$commit

in approval-first mode, defaulting to the whole working tree.

Before starting, load and follow

$commit

. This skill overrides its default scope and approval behavior;

$commit

owns working-tree inspection, grouping, message style, staging, committing, and reporting.

Selected installs do not install dependencies automatically. If

$commit

is not installed or available, stop before staging or committing. Tell the user to install it with:

bash

npx skills add LegendApp/legend-skills --skill commit

Then ask them to retry after installation.

仅在遵循前文所述的显式主动选择启用规则后，才可使用本包装器。常规的审批优先提交请求并不意味着自动启用本技能或其默认的全工作区模式。

使用本技能可让

$commit

以审批优先模式运行，默认覆盖整个工作区。

开始使用前，请加载并遵循

$commit

的规则。本技能仅覆盖其默认范围和审批行为；工作区检查、变更分组、提交信息格式、暂存、提交及报告等核心功能仍由

$commit

负责。

选择安装本技能时不会自动安装依赖项。若

$commit

未安装或不可用，请在暂存或提交前停止操作。告知用户通过以下命令安装：

bash

npx skills add LegendApp/legend-skills --skill commit

然后请用户安装完成后重试。

Scope And Approval Override

范围与审批覆盖规则

When using

$commit

, force plan mode:

Unless the user requests a narrower scope, use all-changes mode: inspect staged, unstaged, and untracked changes as the pool to group. Preserve explicit exclusions.
If the user names a subset or asks for only the current agent's changes, honor that narrower scope.
Always present a commit plan first and wait for explicit approval such as
```
go
```
.
Do not stage or commit before approval, even if there is only one logical commit.
After approval, create all agreed commits without asking again unless the working tree changes unexpectedly.
Treat
```
go
```
after a previously presented plan as approval for that plan, then re-check the working tree before staging.

使用

$commit

时，强制启用计划模式：

除非用户要求缩小范围，否则使用全变更模式：检查已暂存、未暂存及未追踪的变更作为分组池。保留用户明确指定的排除项。
若用户指定了子集或仅要求处理当前agent的变更，则遵循该缩小后的范围。
始终先展示提交计划，等待用户的明确审批（如“go”指令）。
获得审批前不得暂存或提交，即使只有一个逻辑提交项。
获得审批后，创建所有已确认的提交，除非工作区意外变更，否则无需再次询问。
若用户针对之前展示的计划发送“go”指令，视为批准该计划，随后在暂存前重新检查工作区。