commitizen

Validate commit messages and enforce Git flow branch naming conventions.

1|Updated Oct 12, 2022
One-click install
npx skills add https://github.com/plastikaweb/plastikspace --skill commitizen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commitizen
Source: https://github.com/plastikaweb/plastikspace/tree/main/.agent/skills/commitizen
Command: npx skills add https://github.com/plastikaweb/plastikspace --skill commitizen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit messages are often inconsistent and hard to parse by tooling. This Skill guides and validates commits to follow conventional commits and project standards.

Core Features & Use Cases

  • Guided Commit Messages: Interactively suggest and enforce the correct type, scope, and subject.
  • Structure Enforcement: Ensure the subject line length and optional body/footer follow the conventions.
  • Branch and Workflow Alignment: Align commit messages with standard branch naming and changelog prompts to streamline reviews.

Quick Start

Use the commitizen workflow to craft a properly formatted commit on a feature branch.

Frequently Asked Questions about commitizen

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

FAQPage Schema
How do I automate conventional commit messages in my workflow?

This Skill enforces conventional commit message formatting by validating commit types, scopes, issue references, subject length, body formatting, and footer structure to ensure alignment with Git flow conventions.

What's the best way to enforce branch naming prefixes alongside commit conventions?

This Skill aligns branch naming prefixes with Git flow conventions and guides optional changelog updates to streamline code reviews and maintain project standards.

How do I validate commit message structure including body and footer formatting?

You validate commit message structure by applying this Skill to check your type, scope, issue references, subject length, body formatting, and footer structure against conventional commit standards.

Does this commitizen workflow support standard commit types like feat, fix, and refactor?

Yes, this commitizen workflow supports common conventional commit types including feat, fix, docs, test, refactor, perf, and style, guiding you to select the correct type for each commit.

Can I streamline code reviews by aligning commit messages with changelog prompts?

Yes, you can streamline reviews by using this Skill to align commit messages with standard branch naming and generate optional changelog prompts, ensuring consistency across your software projects.

Why does my commit message fail conventional commits validation?

Your commit message fails conventional commits validation when it lacks the correct type, exceeds subject line length limits, or improperly formats the body, footer, or issue references.