Browse / Productivity Workflow / Git Commit Validator

Git Commit Validator

Generates and validates git commit messages that adhere to strict conventional commit standards, character limits, and content policies.

SkillProductivity WorkflowCommunicationDocs StandardsGithub

The source repository doesn't declare a license. Check its terms before reusing the code.

Key features

  • Includes a workflow for drafting, validating, and regenerating commits using an automated script
  • Validates character limits: 50 for the subject and 72 for body lines
  • Prohibits AI attribution, branding, and emojis in commit messages
  • Enforces the Conventional Commit format for structured messages
  • Provides guidance on best practices for writing imperative subjects and explanatory bodies

Use cases

  • Revising a rejected commit message based on user feedback.
  • Drafting a commit message for a new feature or bug fix.
  • Automating commit message generation in a development workflow.

FAQ

How does this skill improve my workflow?

It automates the tedious process of checking commit message rules. By providing instant validation via a script, it catches errors early, reduces the need for manual revisions, and helps you maintain a consistent, high-quality commit log with minimal effort.

What are the main rules this skill enforces?

The skill enforces four key rules: 1) Strict Conventional Commit format (`type(scope): description`), 2) A 50-character limit for the subject line, 3) A 72-character limit for body lines, and 4) A policy against AI attribution, branding, and emojis in messages.

When should I use this skill?

You should use this skill whenever you're creating a git commit. It's designed to be activated automatically before running `git commit` or when you ask Claude to draft or regenerate a commit message, ensuring every commit meets quality standards.

What does the Git Commit Validator skill do?

This skill helps Claude generate and validate git commit messages. It ensures they follow strict conventional commit standards, meet character limits (50-char subject, 72-char body), and are free of AI attribution or emojis, resulting in a clean and professional git history.