commit-messages

Generate gitmoji-enabled Conventional Commits messages with commitlint rules.

1|Updated Oct 18, 2025

Search Tags:#workflow #commit #pre-commit #lint #gitmoji #conventional-commits #scopes

Ready to run

npx skills add https://github.com/JimmyPaolini/monorepo --skill commit-messages-jimmypaolini

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-messages
Source: https://github.com/JimmyPaolini/monorepo/tree/main/documentation/skills/commit-messages
Command: npx skills add https://github.com/JimmyPaolini/monorepo --skill commit-messages-jimmypaolini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing consistent, standards-compliant commit messages across the monorepo is tedious and error-prone; this skill teaches the required format and rules to pass pre-commit checks and CI validations.

Core Features & Use Cases

Enforces the Conventional Commits header format: <type>(<scope>): <gitmoji> <subject>, with a required leading emoji and optional body and footer.
Validates subject, body, and footer constraints: lowercase types/scopes, 72-char line wrapping, subject non-empty, proper blank lines, and allowed scopes.
Use Case: contributors craft commits that automatically satisfy linting and CI gates across multi-project workstreams.

Quick Start

Provide a commit message that follows the project's Conventional Commits format with a leading gitmoji.

Frequently Asked Questions about commit-messages

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

FAQPage Schema

How do I format conventional commit messages with gitmoji to pass commitlint checks?▼

Conventional commit messages with gitmoji require a header format of type(scope): emoji subject, using lowercase types and scopes, imperative tense, and a maximum 72-character subject length to pass commitlint and CI validations.

What are the commitlint rules for subject length and blank lines in conventional commits?▼

Commitlint rules for conventional commits enforce a non-empty subject under 72 characters, lowercase types and scopes, proper imperative tense, and required blank lines separating the header, body, and footer sections.

How do I write a pre-commit ready commit message for a monorepo with multiple scopes?▼

Writing a pre-commit ready message for a monorepo involves specifying a valid lowercase scope matching allowed project boundaries, prefixing the subject with a gitmoji, and wrapping body lines at 72 characters.

Does the conventional commits format require an emoji at the start of the subject?▼

Yes, the conventional commits format in this workflow requires a leading gitmoji at the start of the subject line, immediately following the type and scope declaration, to satisfy pre-commit checks.

What is the best way to ensure git commit messages meet CI validation gates across multiple projects?▼

Ensuring commit messages meet CI validation gates requires following the conventional commits standard with a leading gitmoji, enforcing lowercase types, valid scopes, 72-character line wrapping, and proper blank line spacing.

Why do my conventional commit messages fail linting when adding a body and footer?▼

Conventional commit messages fail linting when required blank lines between the header, body, and footer are missing, or when body lines exceed the 72-character wrapping limit defined by commitlint rules.