knowns.commit

Create Conventional Commits messages from staged changes with confirmation.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/tung68nt/tulie_lab --skill knowns-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowns.commit
Source: https://github.com/tung68nt/tulie_lab/tree/main/.claude/skills/knowns.commit
Command: npx skills add https://github.com/tung68nt/tulie_lab --skill knowns-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

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

Core Features & Use Cases

  • Enforces Conventional Commits: Guides users to create commits with specific types (feat, fix, docs, etc.) and scopes.
  • Verification Step: Prompts users to review staged changes and the generated commit message before finalizing.
  • Use Case: When you've completed a new feature, use this Skill to generate a commit message like feat(auth): implement two-factor authentication with a clear description of the changes.

Quick Start

Use the knowns.commit skill to commit your staged changes with a feature type and an authentication scope.

Frequently Asked Questions about knowns.commit

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

FAQPage Schema
How do I write a conventional commit message for staged Git changes?

The conventional commits specification requires structuring Git commit messages with a specific type and scope, such as feat or fix. This standard improves version history consistency and enables automated changelog generation.

How do I generate a commit message with a specific type and scope?

You can generate a commit message with a type and scope by using a guided process that reviews staged changes and suggests a format like feat(auth): implement feature. This structured approach maintains a clean and automated changelog.

Can I review the generated commit message before executing the Git commit?

Yes, the process includes a mandatory verification step that prompts you to review staged changes and the generated conventional commit message. You must provide confirmation before the commit is executed.

Why use conventional commits for version control history?

Using conventional commits for version control history enforces a standardized specification that improves clarity, consistency, and automation potential. This practice maintains a clean project timeline and enables automated changelog generation.

Do I need to manually stage files before creating a conventional commit?

Yes, you need to stage files manually before creating a conventional commit. The process focuses on reviewing already staged Git changes and generating the structured message, requiring your files to be staged beforehand.