commit

Generate Conventional Commits messages with type, scope, and description.

2|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/elijahmurray/vandra-dev --skill commit-elijahmurray
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/elijahmurray/vandra-dev/tree/main/skills/commit
Command: npx skills add https://github.com/elijahmurray/vandra-dev --skill commit-elijahmurray

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers create Git commits that follow the Conventional Commits specification, ensuring consistency and clarity in the project's commit history.

Core Features & Use Cases

  • Standardized Commit Messages: Generates commit messages with a type (feat, fix, chore, etc.), scope, and description.
  • Automated Formatting: Ensures proper formatting, including breaking lines at 72 characters.
  • Use Case: When you've finished implementing a new feature, use this Skill to generate a commit message like feat(auth): implement JWT authentication.

Quick Start

Use the commit skill to create a conventional commit for your changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages for my Git changes?

Conventional commits standardize your Git history by structuring messages with a type, scope, and description. This specification ensures consistent code changes and enables automated changelog generation across your projects.

What is the correct format for conventional commits in version control?

Conventional commit format requires a type (feat, fix, chore), an optional scope, and a description. Automated formatting ensures proper structure, including breaking lines at 72 characters for consistent version control management.

How do I write a Git commit message when implementing a new feature?

When implementing a new feature, use the feat type with an optional scope and description. This generates standardized Git commit messages like feat(auth): implement JWT authentication to clearly document feature additions.

Does automated commit formatting break lines at 72 characters?

Yes, automated commit formatting breaks lines at 72 characters to ensure proper formatting of conventional commit messages. This maintains consistency and readability across your project's Git commit history and changelogs.

Why use conventional commits for automated changelog generation?

Conventional commits enable automated changelog generation by enforcing a standardized type, scope, and description structure. This consistent format allows version control tools to automatically parse Git history and generate accurate changelogs.