How do I install the Commit skill?

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

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?

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

Commit by tomevault-io — Agent Skill

Name: Commit
Author: tomevault-io

Commit

Create git commits with conventional commit messages. ALWAYS use this skill when committing code - whether user-requested or after completing a task. Triggers on "commit", "/commit", "make a commit", "git commit", "save changes", or any request to commit. Accepts optional context argument for commit message guidance. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Context

Branch: !git branch --show-current
Status: !git status -s
Recent commits: !git log --oneline -5
Staged diff: !git diff --staged -- . ':!*.svg' ':!*lock.json' ':!*lock.yaml' ':!*.lockb' ':!*.lock' ':!.opencode' ':!.claude' ':!.cursor' ':!*.png' ':!*.jpg' ':!*.jpeg' ':!*.gif' ':!*.ico' ':!*.webp' ':!*.avif' ':!*.bmp' ':!*.tiff' ':!*.psd' ':!*.ai' ':!*.eps' ':!*.raw' ':!*.woff' ':!*.woff2' ':!*.ttf' ':!*.eot' ':!*.otf' ':!*.mp3' ':!*.mp4' ':!*.wav' ':!*.ogg' ':!*.webm' ':!*.mov' ':!*.pdf' ':!*.doc' ':!*.docx' ':!*.xls' ':!*.xlsx' ':!*.ppt' ':!*.pptx' ':!*.zip' ':!*.tar.gz' ':!*.gz' ':!*.rar' ':!*.7z' ':!*.bin' ':!*.exe' ':!*.dll' ':!*.so' ':!*.dylib' ':!*.db' ':!*.sqlite' ':!*.sqlite3' ':!*.map' ':!*.js.map' ':!*.css.map' ':!*.min.js' ':!*.min.css' ':!*.bundle.js' ':!*.class' ':!*.jar' ':!*.war' ':!*.pyc' ':!*.pyo' ':!*.whl' ':!*.pem' ':!*.key' ':!*.crt' ':!*.p12' ':!*.parquet' ':!*.pickle' ':!*.npy' ':!*.sketch' ':!*.fig' ':!*.xd'
Staged files: !git diff --staged --name-only

Steps

Analyze — Review staged changes, unstaged modifications, and current branch
Generate — Create commit message following conventional commits: type(scope): message
- Use context if provided: context: $ARGUMENTS
- Types: feat, fix, docs, style, refactor, test, chore
- Infer scope from staged files (e.g., feat(auth): for changes in auth/)
- Match recent commits style when possible
- No co-authors
- Subject line: imperative mood, present tense, lowercase, no period
- Body:
  - Explain why, not what — the diff already shows what changed
  - Use imperative mood and present tense (e.g., "allow users to filter by date" not "allowed" or "allows")
  - Include motivation for the change
  - Contrast with previous behavior when relevant
  - Be specific about user-facing impact — avoid vague messages like "improved experience"; say exactly what changed
- Breaking changes: add ! before the colon in the type prefix (e.g., feat(api)!: remove v1 endpoints) or use a BREAKING CHANGE: footer — MUST be uppercase
Confirm — Ask ALL relevant questions at once:
- No staged files? → "Stage all changes?" / "Select files to stage?"
- Unstaged mods in staged files? → "Include unstaged changes?"
- On main/master? → "Create new branch?" with suggested name
- Show commit message → "Approve?" / "Edit message?"
- "Push after commit?" → Yes/No
Execute — Apply user choices, commit, and push if requested
Handle failures — If commit/push fails:
- Report the error clearly
- Never use --no-verify to bypass hooks
- Suggest fixes (e.g., fix lint errors, resolve conflicts)
- Retry after user addresses the issue

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

---name: commit-32description: Create git commits with conventional commit messages. ALWAYS use this skill when committing code - whether user-requested or after completing a task. Triggers on "commit", "/commit", "make a commit", "git commit", "save changes", or any request to commit. Accepts optional context argument for commit message guidance. Use when this capability is needed.---## Context- Branch: !`git branch --show-current`- Status: !`git status -s`- Recent commits: !`git log --oneline -5`- Staged diff: !`git diff --staged -- . ':!*.svg' ':!*lock.json' ':!*lock.yaml' ':!*.lockb' ':!*.lock' ':!.opencode' ':!.claude' ':!.cursor' ':!*.png' ':!*.jpg' ':!*.jpeg' ':!*.gif' ':!*.ico' ':!*.webp' ':!*.avif' ':!*.bmp' ':!*.tiff' ':!*.psd' ':!*.ai' ':!*.eps' ':!*.raw' ':!*.woff' ':!*.woff2' ':!*.ttf' ':!*.eot' ':!*.otf' ':!*.mp3' ':!*.mp4' ':!*.wav' ':!*.ogg' ':!*.webm' ':!*.mov' ':!*.pdf' ':!*.doc' ':!*.docx' ':!*.xls' ':!*.xlsx' ':!*.ppt' ':!*.pptx' ':!*.zip' ':!*.tar.gz' ':!*.gz' ':!*.rar' ':!*.7z' ':!*.bin' ':!*.exe' ':!*.dll' ':!*.so' ':!*.dylib' ':!*.db' ':!*.sqlite' ':!*.sqlite3' ':!*.map' ':!*.js.map' ':!*.css.map' ':!*.min.js' ':!*.min.css' ':!*.bundle.js' ':!*.class' ':!*.jar' ':!*.war' ':!*.pyc' ':!*.pyo' ':!*.whl' ':!*.pem' ':!*.key' ':!*.crt' ':!*.p12' ':!*.parquet' ':!*.pickle' ':!*.npy' ':!*.sketch' ':!*.fig' ':!*.xd'`- Staged files: !`git diff --staged --name-only`## Steps1. **Analyze** — Review staged changes, unstaged modifications, and current branch2. **Generate** — Create commit message following conventional commits: `type(scope): message` - Use context if provided: `context: $ARGUMENTS` - Types: `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore` - Infer scope from staged files (e.g., `feat(auth):` for changes in `auth/`) - Match recent commits style when possible - No co-authors - **Subject line**: imperative mood, present tense, lowercase, no period - **Body**: - Explain **why**, not **what** — the diff already shows what changed - Use imperative mood and present tense (e.g., "allow users to filter by date" not "allowed" or "allows") - Include motivation for the change - Contrast with previous behavior when relevant - Be specific about user-facing impact — avoid vague messages like "improved experience"; say exactly what changed - **Breaking changes**: add **!** before the colon in the type prefix (e.g., `feat(api)!: remove v1 endpoints`) or use a `BREAKING CHANGE:` footer — MUST be uppercase3. **Confirm** — Ask ALL relevant questions at once: - No staged files? → "Stage all changes?" / "Select files to stage?" - Unstaged mods in staged files? → "Include unstaged changes?" - On main/master? → "Create new branch?" with suggested name - Show commit message → "Approve?" / "Edit message?" - "Push after commit?" → Yes/No4. **Execute** — Apply user choices, commit, and push if requested5. **Handle failures** — If commit/push fails: - Report the error clearly - Never use `--no-verify` to bypass hooks - Suggest fixes (e.g., fix lint errors, resolve conflicts) - Retry after user addresses the issue---> Converted and distributed by [TomeVault](https://tomevault.io/claim/luisurrutia) — claim your Tome and manage your conversions.

Frequently asked questions