How do I install the Git Commit skill?

Run npx skillmds@latest add tomevault-io/git-commit-26 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.

Is Git Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git 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 Git Commit free to use?

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

Who published Git Commit?

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

Git Commit by tomevault-io — Agent Skill

Name: Git Commit
Author: tomevault-io

Git Commit

Create Git commit messages following Conventional Commits format with automatic type and scope detection. Use when asked to "commit changes", "create a commit", "write commit message", or when ready to commit staged code. Supports feat, fix, docs, refactor, test, build, ci, chore, and revert types with project-specific scope determination based on file paths and directory structure. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Git Commit Skill

This skill guides the creation of Git commit messages that follow the Conventional Commits format.

When to Use

Use this skill when:

Code changes are completed and ready to be committed
Need to create a commit message that adheres to project conventions

Commit Message Format

The commit message must follow this format:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Instructions

Check the staged files using git diff --staged --name-only. Ask user to stage changes if there are no staged files.
Determine the appropriate commit type based on the staged files.

type must be selected from the following options:

feat: New feature or change to existing functionality
fix: Bug fix
docs: Documentation-only changes (e.g., changes to *.md files)
refactor: Refactoring (code changes that neither fix a bug nor add a feature)
perf: Performance improvements
test: Adding or modifying tests (e.g., changes to *.spec.* or *.spec.*.snap files)
build: Changes affecting the build system or external dependencies
ci: Changes to CI configuration files (e.g., changes within .github/actions or .github/workflows)
chore: Other changes (e.g., changes to *.json, *.config.mjs, *.config.cjs, *.config.js, *.config.ts, .gitignore, .gitattributes, .prettierignore, .prettier)
revert: Reverting a previous commit

Determine the appropriate scope based on the staged files and the project structure.

scope should be determined based on the directory structure of the staged files. For example:

If staged files are in .claude/ or .mcp.json, use claude
If staged files are in .github/, use github
If staged files are in .vscode/, use vscode
If staged files are in apps/frontend/, use frontend
If staged files are in libs/frontend/feature-xxx, use frontend-feature-xxx
If staged files are in libs/utils/, use utils
If staged files are in the root directory, do not set a scope

Craft a comprehensive and descriptive commit message strictly following the Conventional Commits format.

Important NEVER include \n in the commit message. Always use actual newlines to separate the subject, body, and footer.

Example:

git commit -m "feat(utils): update xxx function

- Add xxx logic in xxx function
- Implement unit tests for xxx function

Co-Authored-By: Copilot <175728472+Copilot@users.noreply.github.com>"

Notes

Important Commit messages must be written in English.
If there are staged changes, determine the commit message based only on the staged changes.
Always include Co-Authored-By information. The commit message must clearly indicate that it was created with Copilot.

References

Commit message

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: git-commit-26description: Create Git commit messages following Conventional Commits format with automatic type and scope detection. Use when asked to "commit changes", "create a commit", "write commit message", or when ready to commit staged code. Supports feat, fix, docs, refactor, test, build, ci, chore, and revert types with project-specific scope determination based on file paths and directory structure. Use when this capability is needed.---# Git Commit SkillThis skill guides the creation of Git commit messages that follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) format.## When to UseUse this skill when:- Code changes are completed and ready to be committed- Need to create a commit message that adheres to project conventions## Commit Message FormatThe commit message must follow this format:```<type>[optional scope]: <description>[optional body][optional footer(s)]```## Instructions1. Check the staged files using `git diff --staged --name-only`. Ask user to stage changes if there are no staged files.2. Determine the appropriate commit type based on the staged files.**type** must be selected from the following options:- `feat`: New feature or change to existing functionality- `fix`: Bug fix- `docs`: Documentation-only changes (e.g., changes to `*.md` files)- `refactor`: Refactoring (code changes that neither fix a bug nor add a feature)- `perf`: Performance improvements- `test`: Adding or modifying tests (e.g., changes to `*.spec.*` or `*.spec.*.snap` files)- `build`: Changes affecting the build system or external dependencies- `ci`: Changes to CI configuration files (e.g., changes within `.github/actions` or `.github/workflows`)- `chore`: Other changes (e.g., changes to `*.json`, `*.config.mjs`, `*.config.cjs`, `*.config.js`, `*.config.ts`, `.gitignore`, `.gitattributes`, `.prettierignore`, `.prettier`)- `revert`: Reverting a previous commit3. Determine the appropriate scope based on the staged files and the project structure.**scope** should be determined based on the directory structure of the staged files. For example:- If staged files are in `.claude/` or `.mcp.json`, use `claude`- If staged files are in `.github/`, use `github`- If staged files are in `.vscode/`, use `vscode`- If staged files are in `apps/frontend/`, use `frontend`- If staged files are in `libs/frontend/feature-xxx`, use `frontend-feature-xxx`- If staged files are in `libs/utils/`, use `utils`- If staged files are in the root directory, do not set a scope4. Craft a comprehensive and descriptive commit message strictly following the Conventional Commits format.**Important** NEVER include `\n` in the commit message. Always use actual newlines to separate the subject, body, and footer.Example:```bashgit commit -m "feat(utils): update xxx function- Add xxx logic in xxx function- Implement unit tests for xxx functionCo-Authored-By: Copilot <175728472+Copilot@users.noreply.github.com>"```## Notes- **Important** Commit messages must be written in English.- If there are staged changes, determine the commit message based only on the staged changes.- Always include `Co-Authored-By` information. The commit message must clearly indicate that it was created with Copilot.## References- [Commit message](./references/commit-message.instructions.md)---> Converted and distributed by [TomeVault](https://tomevault.io/claim/puku0x) — claim your Tome and manage your conversions.

Frequently asked questions