mcpField
C
commit-confirm

commit-confirm

github.com/legendappDevelopment38394 installsUpdated 5d ago
Repository

About commit-confirm

commit-confirm is a wrapper skill that invokes commit in approval-first mode, using the whole working tree by default unless a narrower scope is requested. It requires explicit opt-in and waits for approval before staging or committing.

Key features

  1. 01Invoke commit in approval-first mode
  2. 02Default to the whole working tree
  3. 03Honor explicitly narrower scopes
  4. 04Require approval before staging

Use cases

  1. 01Review a commit plan before changes are committed
  2. 02Group whole-tree changes after explicit opt-in
  3. 03Limit a planned commit to a requested subset

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/legendapp/legend-skills --skill commit-confirm

After installing, type/commit-confirmin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

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:

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

Then ask them to retry after installation.

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.

Comments

Markdown supported