mcpField
W
w-commit

w-commit

github.com/blockmaticDevelopment1647 installsUpdated 4w ago
Repository

About w-commit

w-commit is an agent skill for preparing and creating scoped Git commits. It checks changes, stages only task-owned work, follows Conventional Commit conventions, and does not treat a commit request as permission to push.

Key features

  1. 01Reviews staged and unstaged changes
  2. 02Separates task work from unrelated changes
  3. 03Stages explicit paths or hunks
  4. 04Formats Conventional Commit messages
  5. 05Inspects commit and remaining worktree

Use cases

  1. 01Creating a commit without including unrelated files
  2. 02Checking documentation updates before committing
  3. 03Keeping credentials and secrets out of staging

Install

Copy the command and run it in a terminal.

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

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

Bundled filesreferences/git-publish.md

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