mcpField
W
w-commit

w-commit

github.com/blockmatic-iceboxDevelopment1647 installsUpdated 4w ago
Repository

About w-commit

w-commit is a Basilic workflow skill for agents handling Git commit requests. It emphasizes scoped staging, Conventional Commit messages, and inspecting the resulting commit without treating a request to commit as permission to push.

Key features

  1. 01Inspect staged and unstaged changes
  2. 02Separate task work from unrelated changes
  3. 03Stage explicit paths or hunks
  4. 04Use Conventional Commit messages
  5. 05Review commit and working tree

Use cases

  1. 01Preparing a scoped commit from a mixed working tree
  2. 02Keeping unrelated and secret files out of a commit
  3. 03Checking changes and documentation before committing

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/blockmatic-icebox/basilic-skills --skill w-commit

After installing, type/w-commitin Claude Code to confirm it loaded.

Details

From the project README

Invocation requests a commit. Inspect staged and unstaged changes and the authorized task scope before staging anything. Follow git publish.

  1. If creating a new branch, git fetch origin then git switch -c <name> --no-track origin/main first — never skip fetch, never a stale local main. Inspect the diff and distinguish task-owned changes from unrelated work, including pre-staged files. If the intended commit cannot be separated safely, clarify the file scope.
  2. Before staging: if behavior, commands, or conventions changed, matching MDX and nearest README must be in the diff; otherwise one line why not. Rely on commit hooks. Never the full pre-push suite.
  3. Stage explicit task-owned paths or hunks. Do not sweep unrelated or untracked work into the commit with a blanket add. Never git add -A. Never stage .env, credentials, or secrets.
  4. Write a Conventional Commit: lowercase type/scope, imperative summary of at most 60 characters, no period. Follow repository-specific scope conventions. Pass the message via a heredoc; commit with hooks enabled.
  5. Inspect the result and remaining working tree. Return commit ID and scope. A commit request alone does not authorize pushing.

Comments

Markdown supported