conventional-commit

Conventional commits enforce a standardized format (type: scope?: subject) across all project changes. This eliminates inconsistency, improves readability of project history, and makes it easier to track what changed and why. This Skill generates compliant messages automatically based on your staged changes.

Conventional commits follow a structured format—type (fix, feat, style, build, etc.), optional scope, and lowercase imperative subject—that makes commit history machine-readable and human-friendly. Use it when you need predictable, searchable project history and automated changelog generation.

Yes. This Skill inspects your staged Git changes and diffs, determines the appropriate commit type and scope, then generates a properly formatted message with the correct prefix. You provide the latest changes; it outputs a compliant conventional commit.

This Skill verifies staged changes against conventional-commit rules and suggests corrections when needed. It checks that your message structure matches the required format—type, optional scope, and imperative subject line—before committing.

Yes. This Skill handles multiple change scenarios—bug fixes (fix type), content updates (content scope), style refinements (style type), and build configuration changes (build type)—each with the appropriate conventional prefix and scope for your Quartz blog repository.

Conventional commits provide project-wide consistency by enforcing a single format everyone follows. This Skill automates compliance, removing guesswork and ensuring every commit—whether for posts, code, or configuration—adheres to the same standard your team expects.