w-commit
Review and commit the task's intended changes using repository conventions.
- Installs
- 647
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/blockmatic/basilic-skills --skill w-commit- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads w-commit automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Invocation requests a commit. Inspect staged and unstaged changes and the authorized task scope before staging anything. Follow git publish.
- If creating a new branch,
git fetch originthengit switch -c <name> --no-track origin/mainfirst — never skip fetch, never a stale localmain. 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. - 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.
- 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. - 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.
- Inspect the result and remaining working tree. Return commit ID and scope. A commit request alone does not authorize pushing.
FAQ
What does the w-commit skill do?
Review and commit the task's intended changes using repository conventions.
How do I install w-commit?
Run npx skills add https://github.com/blockmatic/basilic-skills --skill w-commit in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/w-commit/ (personal) or .claude/skills/w-commit/ (project).
Which AI agents can use w-commit?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is w-commit safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains w-commit?
It is published by blockmatic in blockmatic/basilic-skills. It has 647 recorded installs.
More from blockmatic/basilic-skills
workflow
blockmatic/basilic-skills
Basilic /w- playbooks packed so install lands at .agents/skills/workflow/w-plan and the rest.
w-review-plan
blockmatic/basilic-skills
Review a plan's Goals, Assumptions, Tasks, Risks, and References.
w-git-repair
blockmatic/basilic-skills
Resolve common Git problems and conflicts with inspected commands.
w-perf
blockmatic/basilic-skills
Measure bottlenecks with repository tools, then recommend or apply evidenced optimizations.
w-api-test
blockmatic/basilic-skills
Add API tests that exercise public HTTP behavior against existing harnesses.
w-architecture
blockmatic/basilic-skills
Plan an implementation structure; durable decisions belong in ADRs and architecture docs.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.