kn-commit

Inspect staged changes, generate conventional commit messages, and execute git commit after confirmation.

234|50|Updated Dec 25, 2025

Search Tags:#automation #git #commit #developer-tools #code-review #version-control #conventional-commit

Ready to run

npx skills add https://github.com/knowns-dev/knowns --skill kn-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kn-commit
Source: https://github.com/knowns-dev/knowns/tree/main/.agent/skills/kn-commit
Command: npx skills add https://github.com/knowns-dev/knowns --skill kn-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures commits follow a conventional format and are verified before they are saved to the repository, reducing ambiguity and review overhead.

Core Features & Use Cases

Enforces conventional commit messages for staged changes.
Prompts for user confirmation before committing to prevent accidental commits.
Supports common types like feat, fix, docs, style, refactor, perf, test, chore.
Use case: when preparing a feature branch, kn-commit helps generate a compliant commit message and requires your confirmation before executing git commit.

Quick Start

Invoke the workflow by reviewing your staged changes, composing a conventional commit message, confirming, and then executing git commit with that message. Example: feat(auth): add user login

Frequently Asked Questions about kn-commit

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

FAQPage Schema

How do I generate conventional commit messages for staged git changes?▼

To generate conventional commit messages for staged git changes, you can use automation tools that inspect your staged diff and format the output into standard prefixes like feat, fix, or docs before executing git commit.

When do I need to use conventional commits in my version control workflow?▼

You need to use conventional commits in your version control workflow when your team enforces deterministic, auditable history and wants to reduce ambiguity and review overhead by standardizing commit message formats.

Can I review and confirm a conventional commit message before it is executed?▼

Yes, automated conventional commit workflows can prompt for user confirmation before executing git commit, ensuring you review the generated message and preventing accidental commits to the repository.

What conventional commit types are supported by automated commit message generators?▼

Automated commit message generators commonly support conventional commit types including feat, fix, docs, style, refactor, perf, test, and chore to categorize staged changes accurately.

Does automated conventional commit generation require any external dependencies?▼

No, automated conventional commit generation can operate without external dependencies, directly inspecting staged changes and invoking git commit with the formatted message natively.

What is the best way to enforce conventional commit standards across a development team?▼

The best way to enforce conventional commit standards is to automate message generation and require confirmation before committing, ensuring every staged change follows the specified format deterministically.