vcs-commit

Standardize Git commit messages according to the Conventional Commits specification.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/diegocanepa/agent-skills --skill vcs-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vcs-commit
Source: https://github.com/diegocanepa/agent-skills/tree/main/skills/vcs-commit
Command: npx skills add https://github.com/diegocanepa/agent-skills --skill vcs-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures all Git commits adhere to the Conventional Commits specification, making your commit history clear, consistent, and machine-readable.

Core Features & Use Cases

  • Enforces Conventional Commits: Guides users to structure commits with type, scope, description, body, and footers.
  • Supports GitHub/GitLab Mapping: Facilitates integration with platform-specific issue tracking.
  • Use Case: When fixing a bug, you can use this skill to draft a commit message like fix: resolve login issue on user profile page Closes #123.

Quick Start

Draft a git commit message for a new feature that improves user authentication.

Frequently Asked Questions about vcs-commit

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

FAQPage Schema
What is a conventional commit and how does it structure Git commit messages?

A conventional commit structures Git commit messages using a specific format with a type, optional scope, description, body, and footers. This standardized format makes commit history clear, consistent, and machine-readable for version control management.

How do I write a conventional commit message for a bug fix linked to a GitHub issue?

To write a conventional commit for a bug fix, use the fix type followed by a description and footer. For example, `fix: resolve login issue on user profile page` with `Closes #123` in the footer maps the commit to your GitHub or GitLab issue tracking system.

Does the conventional commits format enforce specific grammatical rules for the description?

Yes, the conventional commits format enforces the imperative mood for commit descriptions. It applies specific formatting rules across the type, scope, body, and footers to ensure your Git history remains consistent and machine-readable.

Can I use conventional commits to automate semantic versioning for my project?

Yes, structuring Git commits with conventional commits supports semantic versioning by making your commit history machine-readable. The distinct commit types and formatting rules allow automated tools to parse features and fixes to determine version bumps.

What precautions are in place to prevent accidental data loss when standardizing Git workflows?

A Git Safety Protocol is included to prevent accidental data loss or security breaches during version control management. This protocol enforces specific formatting rules and safety checks while standardizing your commit messages.