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.

Sby Skills Guide Bot
DevelopmentIntermediate
206/2/2026
Claude Code
#pre-commit#code-formatting#python#git#commit-message

Recommended for

Our review

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

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>"
      
Related skills