kn-commit

Enforce Conventional Commits formatting for Git commit messages.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ducanhnguyen223/birthday --skill kn-commit-ducanhnguyen223
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kn-commit
Source: https://github.com/ducanhnguyen223/birthday/tree/main/.claude/skills/kn-commit
Command: npx skills add https://github.com/ducanhnguyen223/birthday --skill kn-commit-ducanhnguyen223

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all code commits adhere to the Conventional Commits specification, improving the clarity and consistency of your project's commit history.

Core Features & Use Cases

  • Enforces Conventional Commits: Guides you to format commit messages correctly with type, scope, and a descriptive message.
  • Verification: Prompts you to review staged changes and confirm the commit message before execution.
  • Use Case: Before pushing your latest feature, use this Skill to ensure your commit message is properly formatted (e.g., feat(auth): add JWT token refresh) and includes a summary of the changes.

Quick Start

Use kn-commit to commit your staged changes with a conventional commit message.

Frequently Asked Questions about kn-commit

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

FAQPage Schema
How do I format conventional commit messages for git?

Format conventional commit messages by structuring your git commit title with a specific type, an optional scope in parentheses, and a descriptive message. This enforces the Conventional Commits specification to standardize your version control history.

What is the conventional commits specification used for in version control?

The conventional commits specification is used to standardize commit messages in version control, ensuring a clear project history. This standardized format enables automated changelog generation and semantic versioning for development workflows.

How do I commit staged changes with a conventional commit message?

To commit staged changes, the Skill guides you to review the staged code, formulate a conventional commit message including a summary of the changes, and prompts you to confirm the message before executing the git commit.

Does this tool verify my code changes before executing the git commit?

Yes, the tool verifies your code changes by prompting you to review staged changes and confirm the commit message before execution. This verification step ensures your commit adheres to specific formatting rules before being finalized.

When do I need to use conventional commits in my development workflow?

You need to use conventional commits in development workflows requiring standardized commit messages for automated changelog generation and semantic versioning. It enforces specific formatting rules for commit titles and bodies to improve commit history clarity.