How do I install the Commit Changes skill?

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

Commit Changes

Creates git commits with comprehensive, Conventional Commits-formatted messages. Use when the user asks to commit, stage changes, save progress, or create a commit message. Ensures consistent, descriptive commit messages following project conventions.

tomevault-io Updated Sep 17, 2026

File contents

Commit Changes — Revela Project

Create git commits with comprehensive messages following Conventional Commits and project conventions.

Do NOT commit automatically. Always show the staged changes and proposed message first. Let the user confirm or adjust before executing.

Step 1: Review Changes

Run git diff --stat (unstaged) and git diff --cached --stat (staged) to understand what changed. If nothing is staged, suggest what to stage based on logical grouping.

Step 2: Compose Commit Message

Format

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

<body>

Subject Line (required)

Type — one of:

Type	Use for
`feat`	New feature, new capability
`fix`	Bug fix
`docs`	Documentation only (copilot-instructions, website, README, skills)
`refactor`	Code restructuring without behavior change
`perf`	Performance improvement
`test`	Adding or fixing tests
`build`	Build system, CI/CD, dependencies, scripts
`chore`	Maintenance tasks that don't fit elsewhere

Scope (optional) — affected area in parentheses: plugin, theme, images, lqip, cli, config, website, sdk, etc.
Subject — imperative mood, lowercase, no period, max 72 chars
- Good: add EXIF extraction for AVIF files
- Bad: Added EXIF extraction for AVIF files.

Body (required for non-trivial changes)

Blank line after subject
Explain what changed and why (not how — the diff shows how)
Use bullet points (-) for multiple changes
Group related changes under headings if the commit covers multiple areas
Wrap lines at 72 characters
Reference issue numbers where applicable: Fixes #42

Examples

Simple change:

fix(serve): use correct default port 8080 in help text

Feature with body:

feat(images): switch from Resize() to ThumbnailImage()

Based on libvips maintainer recommendation (libvips/libvips#4588).
ThumbnailImage() properly handles alpha premultiplication for
transparent PNGs, which Resize() does not.

Multi-area change with grouped body:

docs: comprehensive website and documentation review

User Journey (00):
- Fix serve port: 5000 → 8080 (matches ServeConfig default)
- Fix command: revela generate → revela generate all

Configuration (07):
- Fix image config: remove non-existent 'formats' wrapper
- Use correct flat properties: webp, jpg, avif under generate.images

Deployment (09):
- Fix config section: site.basepath → project.basePath

Step 3: Present to User

Show the proposed commit:

Files to be staged (if not yet staged)
The full commit message
The git commands to execute

Wait for user confirmation before running any git commands.

Rules

One logical change per commit — don't mix unrelated changes
Never commit generated files (artifacts/, playground/standalone-*)
Never commit secrets or user-specific config
Check .gitignore is respected
If changes span multiple logical units, suggest splitting into separate commits

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

---name: commit-changesdescription: Creates git commits with comprehensive, Conventional Commits-formatted messages. Use when the user asks to commit, stage changes, save progress, or create a commit message. Ensures consistent, descriptive commit messages following project conventions.---# Commit Changes — Revela ProjectCreate git commits with comprehensive messages following [Conventional Commits](https://www.conventionalcommits.org/) and project conventions.**Do NOT commit automatically.** Always show the staged changes and proposed message first. Let the user confirm or adjust before executing.## Step 1: Review ChangesRun `git diff --stat` (unstaged) and `git diff --cached --stat` (staged) to understand what changed.If nothing is staged, suggest what to stage based on logical grouping.## Step 2: Compose Commit Message### Format```<type>(<scope>): <subject><body>```### Subject Line (required)- **Type** — one of: | Type | Use for | |------|---------| | `feat` | New feature, new capability | | `fix` | Bug fix | | `docs` | Documentation only (copilot-instructions, website, README, skills) | | `refactor` | Code restructuring without behavior change | | `perf` | Performance improvement | | `test` | Adding or fixing tests | | `build` | Build system, CI/CD, dependencies, scripts | | `chore` | Maintenance tasks that don't fit elsewhere |- **Scope** (optional) — affected area in parentheses: `plugin`, `theme`, `images`, `lqip`, `cli`, `config`, `website`, `sdk`, etc.- **Subject** — imperative mood, lowercase, no period, max 72 chars - Good: `add EXIF extraction for AVIF files` - Bad: `Added EXIF extraction for AVIF files.`### Body (required for non-trivial changes)- Blank line after subject- Explain **what** changed and **why** (not how — the diff shows how)- Use bullet points (`-`) for multiple changes- Group related changes under headings if the commit covers multiple areas- Wrap lines at 72 characters- Reference issue numbers where applicable: `Fixes #42`### Examples**Simple change:**```fix(serve): use correct default port 8080 in help text```**Feature with body:**```feat(images): switch from Resize() to ThumbnailImage()Based on libvips maintainer recommendation (libvips/libvips#4588).ThumbnailImage() properly handles alpha premultiplication fortransparent PNGs, which Resize() does not.```**Multi-area change with grouped body:**```docs: comprehensive website and documentation reviewUser Journey (00):- Fix serve port: 5000 → 8080 (matches ServeConfig default)- Fix command: revela generate → revela generate allConfiguration (07):- Fix image config: remove non-existent 'formats' wrapper- Use correct flat properties: webp, jpg, avif under generate.imagesDeployment (09):- Fix config section: site.basepath → project.basePath```## Step 3: Present to UserShow the proposed commit:1. Files to be staged (if not yet staged)2. The full commit message3. The git commands to execute**Wait for user confirmation before running any git commands.**## Rules- **One logical change per commit** — don't mix unrelated changes- **Never commit generated files** (artifacts/, playground/standalone-*)- **Never commit secrets** or user-specific config- Check `.gitignore` is respected- If changes span multiple logical units, suggest splitting into separate commits---> Converted and distributed by [TomeVault](https://tomevault.io/claim/spectara) — claim your Tome and manage your conversions.

Frequently asked questions