How do I install the Commit skill?

Run npx skillmds@latest add hazat/commit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Commit skill do?

Read this skill before making git commits It is listed under Coding & Dev Tools on SkillMD.

Is Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Commit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Commit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Commit?

hazat (@hazat) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Commit by hazat — Agent Skill

Name: Commit
Author: hazat

File contents

Create a git commit for the current changes using Conventional Commits format with a polished, highly descriptive message. If there are commit hooks - do not skip them, it's your responsability to leave things better than they were.

Format

<type>(<scope>): <summary>

type REQUIRED. Use feat for new features, fix for bug fixes. Other common types: docs, refactor, chore, test, perf.
scope OPTIONAL. Short noun in parentheses for the affected area (e.g., api, parser, ui).
summary REQUIRED. Short, imperative, <= 72 chars, no trailing period.

Notes

Body is strongly encouraged — always include one unless the change is trivially obvious (e.g., fixing a typo). The body should explain what changed, why it changed, the approach taken, and any notable decisions. A reader of git log should understand the change without looking at the diff.
Do NOT include breaking-change markers or footers.
Do NOT add sign-offs (no Signed-off-by).
Only commit; do NOT push.
If it is unclear whether a file should be included, ask the user which files to commit.
Treat any caller-provided arguments as additional commit guidance. Common patterns:
- Freeform instructions should influence scope, summary, and body.
- File paths or globs should limit which files to commit. If files are specified, only stage/commit those unless the user explicitly asks otherwise.
- If arguments combine files and instructions, honor both.

Steps

Infer from the prompt if the user provided specific file paths/globs and/or additional instructions.
Review git status and git diff to understand the current changes (limit to argument-specified files if provided).
(Optional) Run git log -n 50 --pretty=format:%s to see commonly used scopes.
If there are ambiguous extra files, ask the user for clarification before committing.
Stage only the intended files (all changes if no files specified).
Run git commit -m "<subject>" (and -m "<body>" if needed).

---name: commitdescription: Read this skill before making git commits---Create a git commit for the current changes using Conventional Commits format with a **polished, highly descriptive** message.If there are commit hooks - do not skip them, it's your responsability to leave things better than they were.## Format`<type>(<scope>): <summary>`- `type` REQUIRED. Use `feat` for new features, `fix` for bug fixes. Other common types: `docs`, `refactor`, `chore`, `test`, `perf`.- `scope` OPTIONAL. Short noun in parentheses for the affected area (e.g., `api`, `parser`, `ui`).- `summary` REQUIRED. Short, imperative, <= 72 chars, no trailing period.## Notes- Body is **strongly encouraged** — always include one unless the change is trivially obvious (e.g., fixing a typo). The body should explain **what** changed, **why** it changed, the approach taken, and any notable decisions. A reader of `git log` should understand the change without looking at the diff.- Do NOT include breaking-change markers or footers.- Do NOT add sign-offs (no `Signed-off-by`).- Only commit; do NOT push.- If it is unclear whether a file should be included, ask the user which files to commit.- Treat any caller-provided arguments as additional commit guidance. Common patterns: - Freeform instructions should influence scope, summary, and body. - File paths or globs should limit which files to commit. If files are specified, only stage/commit those unless the user explicitly asks otherwise. - If arguments combine files and instructions, honor both.## Steps1. Infer from the prompt if the user provided specific file paths/globs and/or additional instructions.2. Review `git status` and `git diff` to understand the current changes (limit to argument-specified files if provided).3. (Optional) Run `git log -n 50 --pretty=format:%s` to see commonly used scopes.4. If there are ambiguous extra files, ask the user for clarification before committing.5. Stage only the intended files (all changes if no files specified).6. Run `git commit -m "<subject>"` (and `-m "<body>"` if needed).

Frequently asked questions

Commit