Skills Guide

Commit Message Summarizer

VerifiedSafe

This skill automates pre-commit tasks: it runs linters, fixes formatting, summarizes changed files, and generates a concise commit message. It then asks the user for approval before committing with sign-off.

Download and use
Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#pre-commit#code-formatting#python#git#commit-message

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

Runs Python formatting checks and generates a commit message before committing changes.

Strengths

  • Automates formatting with black and isort
  • Generates a concise commit message
  • Asks for user approval before committing
  • Includes sign-off for compliance

Limitations

  • Requires the project to use black and isort with uv
  • Only checks Python files
  • Commit message may need manual tweaking
When to use it

When you want to enforce Python code formatting and automate commit messages before each commit.

When not to use it

For non-Python projects or if you prefer manual formatting and commit messages.

Security analysis

Safe
Quality score85/100

The skill runs common development tools (black, isort, git) for linting and pre-commit tasks. Commands are non-destructive, and the git commit is prompted with user review. No exfiltration, obfuscation, or disabling of safety mechanisms. Safe for listing.

No concerns found

How this analysis is made

Examples

Run pre-commit checks
Run pre-commit checks on my Python project before committing.
Format code and commit
Format my Python code with black and isort, then generate a commit message and commit.

name: pre-commit description: Summarize commit messages for recent changes disable-model-invocation: true

The following steps are done before git commit

Instructions

  1. Check if all Python files under the project root directory pass the linter

    # run the following command under the project root directory
uv run black --check --diff . && uv run isort --check --diff .

  2. Handle linting issues, if any; otherwise, skip this step

    1. Show violations and list the diff summary for manual review

    2. Run black and isort to fix these issues

      # run the following command under the project root directory
uv run black . && uv run isort .

  3. Run git status to see changed files

  4. Generate a commit message for users

    • Keep it concise

  5. Ask users if he/she wants to commit these changes on his/her behalf

    • List the commit message for manual review

    • List all changed files for manual review, in case we wrongly include any files

    • Remember to include the sign-off

      git commit -s -m "<your commit message>"
# or
git commit --signoff -m "<your commit message>"

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

openskills read 'commit-message-summarizer-mm8o52f5'

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/commit-message-summarizer-mm8o52f5/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