Skills Guide

Git Commit

VerifiedSafe

Stage relevant changes and create a git commit with a conventional-style message.

Download and use
Sby Skills Guide Bot
DevelopmentBeginner
7/23/2026
Claude Code
#git#commit#version-control#code-hygiene#workflow

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

When the user explicitly invokes /commit, this skill inspects the repository state, selects the relevant files and creates a commit with a concise message that matches the git history's style.

Strengths

  • Runs git status, git diff and git log in parallel to infer the repo's commit style before drafting the message
  • Avoids git add -A / git add . by staging files individually, keeping the commit focused
  • Skips sensitive files (.env, credentials, keys) and large binaries, warning the user instead
  • Strict guardrails: no push, no amend, no --no-verify, no empty commits, no Co-Authored-By trailer

Limitations

  • Only triggers on an explicit /commit invocation, never on its own
  • Does not push or amend, so fixing a failed pre-commit hook always yields a new commit
  • Secret detection and style matching rely on heuristics rather than guaranteed analysis
When to use it

When you want to turn current working changes into a clean commit that matches the repo's conventions, without touching the remote.

When not to use it

If you need to push, rewrite history or bypass a hook, since the skill explicitly forbids all of these.

Security analysis

Safe
Quality score88/100

The skill only instructs local git inspection, staging, and committing, explicitly forbids push/amend/force/no-verify, and includes guardrails against committing secrets. It does not exfiltrate data, run obfuscated payloads, or perform destructive actions.

No concerns found

How this analysis is made

Examples

Basic commit
/commit
Commit with message hint
/commit fix typo in the README install section
Commit after a refactor
/commit refactor auth middleware to drop the deprecated session helper

name: commit description: Stage relevant changes and create a git commit with a conventional-style message. Only runs when the user explicitly invokes /commit.

/commit

Create a git commit for the current changes.

Steps

  1. Run in parallel:
    • git status (no -uall)
    • git diff (staged + unstaged)
    • git log -n 10 --oneline to match the repo's commit style
  2. Review what would be committed:
    • Skip files that likely hold secrets (.env, credentials, keys).
    • Do not blanket-add with git add -A/git add . — stage files by name.
    • If $ARGUMENTS is non-empty, treat it as the commit message (or message hint) from the user.
  3. Draft a concise 1–2 sentence commit message focused on the why. Follow this repo's existing style from git log (the project uses short imperative subjects like "Improve SEO", "Add CLAUDE.md file").
  4. Stage the intended files:
  5. Run git status after to confirm success.
  6. Do not push. Do not amend. If a pre-commit hook fails, fix the root cause and create a new commit.

Guardrails

  • Never use --no-verify, --amend, or force flags.
  • Never commit .env, credentials, or large binaries — warn the user instead.
  • If there is nothing to commit, say so and stop — do not create empty commits.
  • Do not add a Co-Authored-By: Claude trailer. Commits should look authored solely by the user.

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/git-commit-mrx3xzyk/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/git-commit-mrx3xzyk' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/git-commit-mrx3xzyk/download' --output '.skill-downloads/git-commit-mrx3xzyk/SKILL.md.part' && mv '.skill-downloads/git-commit-mrx3xzyk/SKILL.md.part' '.skill-downloads/git-commit-mrx3xzyk/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/git-commit-mrx3xzyk/SKILL.md' && test -s '.skill-downloads/git-commit-mrx3xzyk/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/commit' && cp -R '.skill-downloads/git-commit-mrx3xzyk' '.claude/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/git-commit-mrx3xzyk'

openskills read 'git-commit-mrx3xzyk'

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/git-commit-mrx3xzyk/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

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot