w-commit — Claude Code skill: what it does, how to install
The w-commit Claude Code skill reviews task changes and creates a repository-style commit. It runs when a commit is requested.
MIT 647 installs ★ 1 updated 2026-10-02
npx skills add blockmatic-icebox/basilic-skills --skill w-commit -a claude-codeWhat w-commit does
w-commit compares staged and unstaged work with the task scope, then prepares a commit. It separates task changes from unrelated edits, including files already staged. If those changes cannot be safely split, the skill asks for the file scope to be clarified.
When behavior, commands, or conventions change, matching MDX files and the nearest README must be part of the diff, or the commit needs a short explanation. The skill stages selected paths or hunks only; it excludes secrets and .env. It writes a Conventional Commit message and leaves hooks enabled. It does not run the full pre-push suite.
After committing, it checks the result and the remaining working tree, then returns the commit ID and scope. A request to commit does not authorize pushing to a remote.
What it helps with
- separate task changes from unrelated work
- create commits that follow repository conventions
- keep secrets and unrelated files out of a commit
- report the commit ID and scope
Example prompts for the agent
- Review this task's changes and create a commit.
- Commit only the files that belong to this task.
- Write a Conventional Commit message and show the remaining changes.
How to install w-commit
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-commit -a claude-code2Manually: put the files in place
~/.claude/skills/w-commit/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/w-commit/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-commit -a codex2Manually: put the files in place
.agents/skills/w-commit/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-commit -a cursor2Manually: put the files in place
.cursor/skills/w-commit/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install blockmatic-icebox/basilic-skills skills/workflow/w-commit2Manually: put the files in place
.github/skills/w-commit/SKILL.md1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-commit -a gemini-cli2Platform CLI
gemini skills install https://github.com/blockmatic-icebox/basilic-skills --path skills/workflow/w-commitManually: put the files in place
.devin/skills/w-commit/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-commit -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about w-commit
How do I install w-commit in Claude Code?
Run npx skills add blockmatic-icebox/basilic-skills --skill w-commit -a claude-code. The skill file is at ~/.claude/skills/w-commit/SKILL.md.
What does w-commit do?
It checks changes against the task scope, stages the relevant paths or hunks, and creates a commit that follows repository conventions. It then reports the commit ID and remaining work.
Does w-commit push changes to a remote?
No. A commit request alone does not authorize pushing.
Source text
SKILL.md · MIT
--- name: w-commit description: Review and commit the task's intended changes using repository conventions. disable-model-invocation: true --- Invocation requests a commit. Inspect staged and unstaged changes and the authorized task scope before staging anything. Follow [git publish](references/git-publish.md). 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.
© blockmatic-icebox · MIT · blockmatic-icebox/basilic-skills