git-commits

Standardize Git commit messages using Conventional Commits rules.

1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/micaelmalta/agentic --skill git-commits-micaelmalta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commits
Source: https://github.com/micaelmalta/agentic/tree/main/skills/git-commits
Command: npx skills add https://github.com/micaelmalta/agentic --skill git-commits-micaelmalta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardize commit messages across projects, improving history readability and release traceability.

Core Features & Use Cases

  • Conventional-commit guidance: ensure types, scope, and messages follow defined rules.
  • Changelog & release notes: generate and summarize changes for releases.
  • Versioning & tagging: suggest semantic version bumps and tagging conventions.
  • Use Case: When coordinating a release with a small team, generate consistent commit messages, a changelog, and release notes in one workflow.

Quick Start

Ask the AI to draft a commit message, changelog entry, or release note for your current task. Example: feat(auth): add OAuth login

Frequently Asked Questions about git-commits

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

FAQPage Schema
What are conventional commits and how do they standardize git commit messages?

Conventional commits standardize git commit messages by enforcing rules for commit types, scope formatting, and single-purpose commits. This creates consistent project history, clear changelogs, and reliable release notes across software development teams.

How do I write a conventional commit message for a new feature?

To write a conventional commit message, specify a commit type like 'feat', add a scope in parentheses such as '(auth)', and provide a concise description. An example is 'feat(auth): add OAuth login' to ensure structured git history.

Can I generate changelog entries and release notes from my git repository history?

Yes, you can generate changelog entries and release notes from git repository history. By applying conventional commit guidelines to your messages, the skill summarizes changes and automates release documentation for your software.

Does this conventional commit approach work for small software development teams?

Yes, conventional commits work for small software development teams maintaining Git repositories. It enables you to coordinate releases by generating consistent commit messages, a changelog, and release notes in a single workflow.

What is the best way to suggest semantic version bumps and tagging conventions?

The best way to suggest semantic version bumps and tagging conventions is by following conventional commit types. Using defined commit-type rules ensures that versioning and tagging accurately reflect the scope of changes for each release.