commitlint-config

Conventional commits enforce a standardized `type(scope?): subject` format for commit messages. This Skill configures commitlint to validate messages against conventional commit standards, blocking non-compliant commits via Husky pre-commit hooks, ensuring clarity and machine-readability for automated changelog generation.

Yes. This Skill integrates commitlint configuration with GitHub Copilot by providing relaxed subject rules and a `.copilot-commit-message-instructions.md` template that guides AI-generated messages to comply with conventional commit standards, ensuring Copilot outputs pass validation automatically.

Commitlint requires `@commitlint/cli`, `@commitlint/config-conventional`, and `husky` to be installed. This Skill validates that these dependencies are correctly installed and generates the necessary `commitlint.config.js` and Husky `commit-msg` hook configuration for your repository.

Commit message validation integrates with CI/CD through Husky pre-commit hooks that block non-compliant commits before they reach your pipeline. This Skill sets up the validation rules and hook integration, ensuring only standardized commits are pushed, automating changelog generation and maintaining consistent project history.

Standardized commit messages enable automated changelog generation, improve code history analysis, and support collaboration with AI tools. Conventional commits provide machine-readable structure—type and scope—that tools parse automatically, eliminating manual changelog curation and ensuring consistent project documentation.

Commitlint enforces a single standard by validating every commit message against the conventional commit format and blocking non-compliant messages. This Skill provides Copilot instructions and Husky integration to make compliance automatic, but existing non-standard messages in history remain unchanged; validation applies only to new commits.