How do I install the Commit Changes skill?

Run npx skillmds@latest add tomevault-io/commit-changes-2 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 Commit Changes 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 Changes?

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 Changes free to use?

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

Who published Commit Changes?

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

Commit Changes by tomevault-io — Agent Skill

Name: Commit Changes
Author: tomevault-io

File contents

Commit Task

Create a commit for staged/unstaged changes following project conventions.

Steps

Check git status for changes
Analyze git log --oneline -10 to detect commit style
Categorize changes (feat/fix/docs/refactor/test/chore)
Generate commit message matching detected style
Present to user for approval
Execute commit

Commit Style Detection

Use the detection script for accurate results:

# Returns JSON with style and confidence
"${CLAUDE_PLUGIN_ROOT}/scripts/detect-commit-style.sh"

Output example:

{
  "style": "conventional-scoped",
  "confidence": 80,
  "stats": { "total": 10, "conventional_scoped": 8, "gitmoji": 2 }
}

Pattern	Style
`type(scope): message`	Conventional Commits (scoped)
`type: message`	Conventional (no scope)
`:emoji: message`	Gitmoji
Plain text	Simple

Conventional Commits Types

Type	Use For
feat	New features
fix	Bug fixes
docs	Documentation only
style	Formatting changes
refactor	Code restructuring
perf	Performance improvements
test	Adding/fixing tests
chore	Maintenance tasks

Message Format

<type>(<scope>): <subject>

<body>

<footer>

Subject Rules:

Imperative mood ("add" not "added")
No period at end
Max 50 characters
Lowercase

Body (optional):

Explain what and why
Wrap at 72 characters

Footer (optional):

Closes #123
BREAKING CHANGE: description

Output

Present message for approval before committing.

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

---name: commit-changes-2description: Create a well-formatted commit following project conventions. Auto-detects commit style from git history. Use when this capability is needed.---# Commit TaskCreate a commit for staged/unstaged changes following project conventions.## Steps1. Check `git status` for changes2. Analyze `git log --oneline -10` to detect commit style3. Categorize changes (feat/fix/docs/refactor/test/chore)4. Generate commit message matching detected style5. Present to user for approval6. Execute commit## Commit Style DetectionUse the detection script for accurate results:```bash# Returns JSON with style and confidence"${CLAUDE_PLUGIN_ROOT}/scripts/detect-commit-style.sh"```**Output example:**```json{ "style": "conventional-scoped", "confidence": 80, "stats": { "total": 10, "conventional_scoped": 8, "gitmoji": 2 }}```| Pattern | Style ||---------|-------|| `type(scope): message` | Conventional Commits (scoped) || `type: message` | Conventional (no scope) || `:emoji: message` | Gitmoji || Plain text | Simple |## Conventional Commits Types| Type | Use For ||------|---------|| feat | New features || fix | Bug fixes || docs | Documentation only || style | Formatting changes || refactor | Code restructuring || perf | Performance improvements || test | Adding/fixing tests || chore | Maintenance tasks |## Message Format```<type>(<scope>): <subject><body><footer>```**Subject Rules:**- Imperative mood ("add" not "added")- No period at end- Max 50 characters- Lowercase**Body** (optional):- Explain what and why- Wrap at 72 characters**Footer** (optional):- `Closes #123`- `BREAKING CHANGE: description`## OutputPresent message for approval before committing.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/anilcancakir) — claim your Tome and manage your conversions.

Frequently asked questions

Commit Changes