rule-commit

Enforces conventional commits with schema-specific scopes via commitlint and Husky.

1|Updated Apr 17, 2025
One-click install
npx skills add https://github.com/carrot-foundation/schemas --skill rule-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rule-commit
Source: https://github.com/carrot-foundation/schemas/tree/main/.agents/skills/rule-commit
Command: npx skills add https://github.com/carrot-foundation/schemas --skill rule-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit hygiene is critical for traceability across schemas; this Skill enforces a standardized commit format with schema-specific scopes to improve automation and release accuracy.

Core Features & Use Cases

  • Enforces conventional commit types (feat, fix, docs, chore, etc.) for all commits
  • Supports schema-specific scopes to categorize changes by area (schema, shared, etc.)
  • Integrates with commitlint and Husky to prevent non-conforming commits in CI
  • Improves changelog generation and code review clarity for schema projects

Quick Start

Start by formatting every commit as a conventional type and optional scope, followed by a concise description.

Frequently Asked Questions about rule-commit

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

FAQPage Schema
How do I enforce conventional commits with schema-specific scopes?▼

To enforce conventional commits with schema-specific scopes, this Skill integrates with commitlint and Husky to validate every commit message against your defined naming convention and scope taxonomy, preventing non-conforming commits in CI.

Why does my commitlint CI pipeline fail for invalid scope taxonomy?▼

Your commitlint CI pipeline fails for invalid scope taxonomy because commit messages do not adhere to the defined project guidelines; this Skill enforces standardized schema-specific scopes to ensure traceability and prevent non-conforming commits.

Can I use commitlint and Husky to improve changelog generation for schemas?▼

Yes, you can use commitlint and Husky to improve changelog generation for schemas; this Skill enforces standardized conventional commit formats with schema-specific scopes to improve automation and release accuracy.

Do I need a defined scope taxonomy before enforcing commit rules?▼

Yes, you need a defined commit naming convention and scope taxonomy before enforcing commit rules; this Skill requires these predefined guidelines to ensure every commit adheres to the project standards for schema changes.

What is the best way to standardize commit messages for schema changes?▼

The best way to standardize commit messages for schema changes is to enforce conventional commit types with schema-specific scopes using commitlint and Husky, which improves traceability and release accuracy.