commit

Create git commits following the conventional commit format.

Updated Feb 8, 2026

Search Tags:#git #commit #commitlint #commit message #conventional commit

Ready to run

npx skills add https://github.com/eykd/vance-ts --skill commit-eykd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/eykd/vance-ts/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/eykd/vance-ts --skill commit-eykd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires commitlint, husky, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps manage git commits more effectively by enforcing conventional commit format, ensuring clarity and consistency in commit messages.

Core Features & Use Cases

Conventional Commit Format: Guides users in creating commit messages that follow a standard format, improving code readability and maintainability.
Commit Message Best Practices: Provides rules for line length, formatting, and structure to ensure clear and concise commit messages.
Pre-commit Hook Integration: Assists in setting up pre-commit hooks for linting and type checking to maintain code quality.

Quick Start

Use the commit skill to commit your changes with a conventional commit message, ensuring your commit history is clear and maintainable.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I format git commit messages using conventional commit guidelines?▼

You format conventional commit messages by structuring your commit type, scope, and description according to standard rules. This approach ensures clarity and consistency, improving overall code readability and maintainability across your project history.

What is the conventional commit format and why should I use it for git commits?▼

The conventional commit format is a standard structure for writing git commit messages that specifies the type and scope of changes. Using it ensures clarity in commit messages, which directly improves code readability and maintainability for your team.

Do I need commitlint and husky to enforce conventional commit rules?▼

Yes, you need commitlint and husky to enforce conventional commit rules. This Skill integrates with pre-commit hooks using these dependencies to automate linting checks, ensuring your commit messages meet quality standards before changes are committed.

How do I set up pre-commit hooks for commit message linting?▼

You set up pre-commit hooks for commit message linting by integrating commitlint and husky into your project. This configuration automatically checks your git commits against conventional commit rules to maintain code quality before submission.

What are the best practices for git commit message line length and structure?▼

Best practices for git commit message structure involve following conventional commit formatting, which provides specific rules for line length and formatting. Adhering to these guidelines ensures your commit messages remain clear, concise, and highly readable.