Create Git Commit

VerifiedCaution

Creates a git commit with a properly formatted message following project conventions. Automatically stages changes and generates atomic, descriptive commit subjects. Useful when saving progress or completing a task, ensuring commits are clean and reviewable.

Sby Skills Guide Bot
DevelopmentBeginner
6/2/2026
Claude CodeCursorWindsurfCopilotCodex
#git#commit#version-control#atomic-commits

Recommended for

Automated summary

Creates Git commits following project conventions, with a strict message format and instructions for a clean history.

Strengths

  • Clear and consistent commit messages
  • Encourages atomic commits
  • Avoids anti-patterns like redundancy or implementation journey

Limitations

  • Does not handle merge conflicts
  • May miss full context if message is too short
  • Relies on existing Git configuration (hooks, conventions)
When to use it

Use this skill whenever you need to save changes in Git with a well-formatted commit message.

When not to use it

Do not use it when you need a complex commit with many unrelated changes or when you need to modify existing history.

Security analysis

Caution
Quality score92/100

The skill uses git commands that modify the repository, which is a powerful action. However, it includes safety guidelines to avoid force pushing and amending others' commits, and it does not engage in destructive or exfiltrating behavior. The risk is legitimate for the task.

Findings
  • •The skill instructs the AI to stage and commit changes to the repository, which could result in unintended commits or loss of work if misused.
How this analysis is made

Examples

Commit staged changes
Commit my staged changes with a message following the standard format.
Commit unstaged changes
Create a commit for all unstaged changes with a descriptive subject line.
Commit with body
Commit the current changes with a subject line 'Add user authentication' and a body explaining the new feature.

name: commit description: Use when creating a git commit for staged or unstaged changes. Triggers on "commit this", "save my changes", or when implementation work completes and needs version control.

Commit Changes

Create a git commit following project conventions.

Commit Message Format

Subject line: Imperative mood, 50 chars max, capitalized, no period

  • "Add spectrum analyzer" NOT "Added spectrum analyzer"
  • Test: "If applied, this commit will [your subject]"

Body: Optional. Most commits need only a subject line. When included:

  • State WHAT capability exists after this commit (1-2 sentences max)
  • Skip if subject line is self-explanatory

Anti-patterns (never include):

  • Implementation journey ("was implemented and reverted", "tried X then Y")
  • Redundant expansion of subject ("This adds..." when subject says "Add...")
  • Phase/step references from planning docs
  • Rationale for rejected approaches

Scope: One logical change per commit. Atomic commits simplify review and revert.

Instructions

  1. Run git status and git diff --staged (or git diff if nothing staged) to understand changes
  2. Run git log --oneline -5 to see recent commit style
  3. Draft a commit message following the format above
  4. Stage relevant files and commit:

Simple commit (preferred):

git commit -m "Add vertical offset parameter for linear waveforms"

With body (only when subject needs clarification):

git commit -m "$(cat <<'EOF'
Add vertical offset parameter for linear waveforms

Enables vertical stacking of multiple waveforms in linear mode.
EOF
)"

Safety

  • NEVER amend commits you didn't create (check git log -1 --format='%an %ae')
  • NEVER force push to main/master
  • NEVER skip hooks unless explicitly requested

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/create-git-commit-mma3js1v/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/create-git-commit-mma3js1v' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/create-git-commit-mma3js1v/download' --output '.skill-downloads/create-git-commit-mma3js1v/SKILL.md.part' && mv '.skill-downloads/create-git-commit-mma3js1v/SKILL.md.part' '.skill-downloads/create-git-commit-mma3js1v/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/create-git-commit-mma3js1v/SKILL.md' && test -s '.skill-downloads/create-git-commit-mma3js1v/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/commit' && cp -R '.skill-downloads/create-git-commit-mma3js1v' '.claude/skills/commit'

Cursor
test -f '.skill-downloads/create-git-commit-mma3js1v/SKILL.md' && test -s '.skill-downloads/create-git-commit-mma3js1v/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/commit' && cp -R '.skill-downloads/create-git-commit-mma3js1v' '.cursor/skills/commit'

Codex
test -f '.skill-downloads/create-git-commit-mma3js1v/SKILL.md' && test -s '.skill-downloads/create-git-commit-mma3js1v/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/commit' && cp -R '.skill-downloads/create-git-commit-mma3js1v' '.agents/skills/commit'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/create-git-commit-mma3js1v'

openskills read 'create-git-commit-mma3js1v'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/create-git-commit-mma3js1v/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills