commit-patterns

What problem does it solve?

This Skill standardizes commit messages using Conventional Commits, improving project history readability, enabling automated changelog generation, and streamlining code reviews. It ensures consistent, high-quality communication within your development team.

Core Features & Use Cases

• Conventional Commit Format: Guides on using type(scope): description with predefined types (e.g., feat, fix, refactor, chore) and rules for imperative mood and subject line length.
• Scopes by Project Type: Provides recommended scopes for both Nix and TypeScript projects, ensuring relevant context for each commit.
• Pre-Commit Checklist: Includes steps for checking staged changes, running validation (typecheck, lint, test), and reviewing for secrets before committing, preventing common mistakes.
• Use Case: A developer has completed a new feature and needs to commit their changes. They can use this skill to compose a conventional commit message, ensuring it follows the correct type, scope, and imperative mood, and includes a reference to the associated issue.

Quick Start

Compose a conventional commit message for a new feature that adds 'OAuth2 Google login' to the 'auth' scope, referencing issue #42.