Skills Guide

Standardized Commit

VerifiedCaution

This skill automates staging relevant files and writing commit messages in a conventional format (type: description). It uses git status and diff to decide what to stage and ensures messages are concise, imperative, and under 72 characters. Useful for maintaining consistent commit history without manual formatting.

Download and use
Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#git#commit-messages#version-control#conventional-commits

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

Stages relevant changes and creates a well-formatted commit message following conventional commit standards.

Strengths

  • Automatically stages changes intelligently, grouping related files
  • Enforces a clear, consistent commit message format
  • Reduces cognitive overhead of deciding commit message structure
  • Avoids committing sensitive files like .env automatically

Limitations

  • May not always correctly group unrelated changes if they appear together
  • Relies on the model's judgment for staging, which may occasionally miss files
  • Only supports a fixed set of commit types
When to use it

Use when you want to quickly commit changes with a properly formatted message without manual typing.

When not to use it

Do not use when you need to craft a detailed multi-line commit message or when you want to review staged changes manually.

Security analysis

Caution
Quality score90/100

The skill automates git staging and committing, which is a powerful operation. While it instructs to avoid secret files, the AI's judgment may not be perfect, and the commit happens without user review. No destructive or exfiltrating actions.

Findings
  • •Automatically stages and commits changes without user confirmation, relying on AI to avoid staging secrets. Risk of accidentally committing sensitive files.
How this analysis is made

Examples

Commit staged changes
commit the changes
Commit with specific type
commit these changes as a fix
Commit all current work
stage and commit everything I've done

name: commit description: Stage and commit changes with standardized format user-invocable: true disable-model-invocation: true

Standardized Commit

Current State

!git status --short

!git diff --stat

!git diff --cached --stat

Instructions

Based on the git status and diff above:

  1. Stage changes if not already staged:

    • Stage relevant files (use judgment on what belongs together)
    • Do not stage unrelated changes
    • Do not stage files that likely contain secrets (.env, credentials, tokens)

  2. Write commit message in this format:

    <type>: <description>

    Types:

    • fix: Bug fix
    • feat: New feature
    • refactor: Code restructuring (no behavior change)
    • docs: Documentation only
    • test: Adding/updating tests
    • chore: Build, config, tooling changes

    Rules:

    • Description is lowercase, no period at the end
    • Keep under 72 characters total
    • Be specific: not "fix bug" but "fix null pointer in request handler"
    • Use imperative mood: "add feature" not "added feature"

  3. Commit without asking for confirmation. Use a HEREDOC for the message:

    git commit -m "$(cat <<'EOF'
<type>: <description>
EOF
)"

Examples

Good:

  • fix: handle empty response in sglang backend
  • feat: add per-user rate limiting middleware
  • refactor: extract token validation to separate module
  • docs: update sglang disaggregation deployment guide
  • chore: bump maturin version to 1.8

Bad:

  • Fix bug (too vague, wrong case)
  • Updated code (meaningless, past tense)
  • WIP (not a complete commit)
  • fix: fix the thing. (period, vague)

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

openskills read 'standardized-commit-mmh8qra6'

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/standardized-commit-mmh8qra6/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