clean-code-commit

Validate and generate Conventional Commits messages for git workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill clean-code-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-code-commit
Source: https://github.com/OntoLedgy/ol_ai_context_library/tree/main/skills/clean-code-commit
Command: npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill clean-code-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent or non-compliant commit messages break CI/CD pipelines, make git history difficult to parse, and violate team coding standards, leading to wasted time during code reviews and release audits.

Core Features & Use Cases

  • Commit Message Validation: Checks existing commit messages against the full Conventional Commits specification, flagging issues like invalid types, incorrect casing, overly long descriptions, or missing breaking change markers.
  • Compliant Message Generation: Creates valid Conventional Commits messages from git diffs, lists of changed files, or plain-English change descriptions, auto-inferring the correct commit type, scope, and breaking change status.
  • Use Case: A developer working on a bug fix can use this skill to turn a raw diff of changed authentication files into a properly formatted fix(auth): correct token expiration validation commit message that passes team CI checks, or validate a drafted message before pushing to avoid pipeline failures.

Quick Start

Use the clean-code-commit skill to generate a compliant Conventional Commits message from the diff of your recent changes to the payment processing module.

Frequently Asked Questions about clean-code-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate conventional commit messages from a git diff?

To generate conventional commit messages from a git diff, the skill analyzes your changed files or plain-English descriptions to auto-infer the correct commit type, scope, and breaking change status. This ensures your git history passes CI/CD quality gates and automates changelog generation.

Why do my commit messages fail CI/CD pipeline quality checks?

Your commit messages fail CI/CD pipeline quality checks due to invalid types, incorrect casing, overly long descriptions, or missing breaking change markers. Validating your messages against the conventional commits specification before pushing prevents these pipeline failures and standardizes code reviews.

What is the conventional commits specification for version control?

The conventional commits specification for version control is a standardized format enforcing rules for commit type, scope, description formatting, and footer tokens. It ensures compatibility with versioning and changelog automation tools by requiring explicit breaking change declarations in git history.

How do I validate a drafted commit message before pushing to version control?

To validate a drafted commit message before pushing to version control, the skill checks your message against the full conventional commits specification. It flags issues like invalid types and missing breaking change markers, helping you avoid pipeline failures and maintain consistent git history.

Can I use plain-English change descriptions to create compliant commit messages?

Yes, you can use plain-English change descriptions to create compliant commit messages. The skill auto-infers the correct conventional commits type, scope, and breaking change status from your description, transforming raw text into a properly formatted message that passes team CI checks.