commit

Name: commit
Availability: InStock
Author: DataRoad

Validate Git commit messages against Angular Conventional Commits format.

1|Updated Jan 24, 2026

Search Tags:#changelog #commit #formatting #scope #lint #conventional-commits #git-hooks

Ready to run

npx skills add https://github.com/dataroadinc/rhusky --skill commit-dataroadinc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/dataroadinc/rhusky/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/dataroadinc/rhusky --skill commit-dataroadinc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides teams to create commits that follow the Angular Conventional Commits format, ensuring consistent history and reliable changelog generation.

Core Features & Use Cases

Enforces type, scope, and subject formats for commits
Validates breaking changes markers and mandatory scope naming
Integrates with Git hooks to reject non-conforming commits
Supports downstream tooling for changelog generation (e.g., Cocogitto)

Quick Start

Create a commit using the type(scope): subject format to ensure conventional changelog generation.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I enforce conventional commit messages in Git?▼

You can enforce conventional commit messages by validating the type, scope, and subject according to Angular conventions. This ensures consistent history and reliable changelog generation across routine code changes.

What is the correct format for conventional commits?▼

The correct format for conventional commits is type(scope): subject. This structure enforces strict formatting guidelines for the commit type, mandatory scope naming, and descriptive subject lines.

Can I use Git hooks to reject non-conforming commit messages?▼

Yes, Git hooks can reject non-conforming commit messages automatically. This integration validates breaking change markers and scope naming guidelines, preventing invalid commits from entering your branch history.

How do conventional commits support changelog generation?▼

Conventional commits support changelog generation by standardizing commit structure with validated types and scopes. This consistent history allows downstream tooling to automatically parse changes and generate reliable release notes.

Does this commit validation require a mandatory scope?▼

Yes, this commit validation requires a mandatory scope in the commit message. It enforces strict scope naming guidelines alongside type and breaking-change markers to satisfy Angular conventional formatting requirements.