How do I install the Git Commit skill?

Run npx skillmds@latest add payals/git-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.

Is Git 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 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. This skill is licensed under MIT.

Who published Git Commit?

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

Git Commit by payals — Agent Skill

Name: Git Commit
Author: payals

Git Commit

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

payals f10a064 3.3 KB Updated Sep 17, 2026

File contents

Git Commit with Conventional Commits

Overview

Create standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff using commands likst git status to determine appropriate type, scope, and message. Do not use emdashes or quotations in the git message. Do not run the git commit command yourself. Your task is to compose a well formatted git commit message and give it to the asker.

Conventional Commit Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Commit Types

Type	Purpose
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only
`style`	Formatting/style (no logic)
`refactor`	Code refactor (no feature/fix)
`perf`	Performance improvement
`test`	Add/update tests
`build`	Build system/dependencies
`ci`	CI/config changes
`chore`	Maintenance/misc
`revert`	Revert commit

Breaking Changes

# Exclamation mark after type/scope
feat!: remove deprecated endpoint

# BREAKING CHANGE footer
feat: allow config to extend other configs

BREAKING CHANGE: `extends` key behavior changed

Workflow

1. Analyze Diff

# If files are staged, use staged diff
git diff --staged

# If nothing staged, use working tree diff
git diff

# Also check status
git status --porcelain

2. Stage Files (if needed)

If nothing is staged or you want to group changes differently:

# Stage specific files
git add path/to/file1 path/to/file2

# Stage by pattern
git add *.test.*
git add src/components/*

# Interactive staging
git add -p

Never commit secrets (.env, credentials.json, private keys).

3. Generate Commit Message

Analyze the diff to determine:

Type: What kind of change is this?
Scope: What area/module is affected?
Description: One-line summary of what changed (present tense, imperative mood, <72 chars)

4. Execute Commit

# Single line
git commit -m "<type>[scope]: <description>"

# Multi-line with body/footer
git commit -m "$(cat <<'EOF'
<type>[scope]: <description>

<optional body>

<optional footer>
EOF
)"

Best Practices

One logical change per commit
Present tense: "add" not "added"
Imperative mood: "fix bug" not "fixes bug"
Reference issues: Closes #123, Refs #456
Keep description under 72 characters

Git Safety Protocol

NEVER update git config
NEVER run destructive commands (--force, hard reset) without explicit request
NEVER skip hooks (--no-verify) unless user asks
NEVER force push to main/master
If commit fails due to hooks, fix and create NEW commit (don't amend)

---name: git-commitdescription: Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical groupinglicense: MIT---# Git Commit with Conventional Commits## OverviewCreate standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff using commands likst `git status` to determine appropriate type, scope, and message. Do not use emdashes or quotations in the git message. Do not run the git commit command yourself. Your task is to compose a well formatted git commit message and give it to the asker.## Conventional Commit Format```<type>[optional scope]: <description>[optional body][optional footer(s)]```## Commit Types| Type | Purpose || ---------- | ------------------------------ || `feat` | New feature || `fix` | Bug fix || `docs` | Documentation only || `style` | Formatting/style (no logic) || `refactor` | Code refactor (no feature/fix) || `perf` | Performance improvement || `test` | Add/update tests || `build` | Build system/dependencies || `ci` | CI/config changes || `chore` | Maintenance/misc || `revert` | Revert commit |## Breaking Changes```# Exclamation mark after type/scopefeat!: remove deprecated endpoint# BREAKING CHANGE footerfeat: allow config to extend other configsBREAKING CHANGE: `extends` key behavior changed```## Workflow### 1. Analyze Diff```bash# If files are staged, use staged diffgit diff --staged# If nothing staged, use working tree diffgit diff# Also check statusgit status --porcelain```### 2. Stage Files (if needed)If nothing is staged or you want to group changes differently:```bash# Stage specific filesgit add path/to/file1 path/to/file2# Stage by patterngit add *.test.*git add src/components/*# Interactive staginggit add -p```**Never commit secrets** (.env, credentials.json, private keys).### 3. Generate Commit MessageAnalyze the diff to determine:- **Type**: What kind of change is this?- **Scope**: What area/module is affected?- **Description**: One-line summary of what changed (present tense, imperative mood, <72 chars)### 4. Execute Commit```bash# Single linegit commit -m "<type>[scope]: <description>"# Multi-line with body/footergit commit -m "$(cat <<'EOF'<type>[scope]: <description><optional body><optional footer>EOF)"```## Best Practices- One logical change per commit- Present tense: "add" not "added"- Imperative mood: "fix bug" not "fixes bug"- Reference issues: `Closes #123`, `Refs #456`- Keep description under 72 characters## Git Safety Protocol- NEVER update git config- NEVER run destructive commands (--force, hard reset) without explicit request- NEVER skip hooks (--no-verify) unless user asks- NEVER force push to main/master- If commit fails due to hooks, fix and create NEW commit (don't amend)

Frequently asked questions