commit

Create Git commits adhering to the Conventional Commits specification.

40|5|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/adrhill/asdex --skill commit-adrhill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/adrhill/asdex/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/adrhill/asdex --skill commit-adrhill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating Git commits by enforcing the Conventional Commits specification, ensuring clear, consistent, and machine-readable commit messages.

Core Features & Use Cases

  • Enforces Conventional Commits: Guides users to create commits with types (fix, feat, etc.), scopes, and bodies that adhere to the specification.
  • Automates Git Workflow: Integrates git status, git diff, and git log to help users understand changes before drafting messages, and automates staging and committing.
  • Use Case: A developer needs to commit a bug fix. This Skill will prompt them to describe the fix using the fix: type, ensuring the commit message is clear and can be used for automated changelog generation or semantic versioning.

Quick Start

Use the commit skill to create a commit with the type 'fix' and the description 'resolve login issue'.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write conventional commits for git changes?

Conventional commits enforce structured git messages using types like feat, fix, or chore, plus optional scopes and descriptions. This ensures clear, machine-readable history for automated changelog generation and semantic versioning.

What's the best way to automate git commit messages with conventional commit formatting?

Automating conventional commit messages requires reading git status and diff to understand changes, then drafting a structured message. This Skill integrates those git commands to review staged files and generate compliant messages automatically.

Do I need git command-line tools to use conventional commits automation?

Yes, git command-line tools are required. This Skill relies on the git CLI to execute status, diff, and log commands for analyzing repository changes before staging and committing them with conventional message formatting.

Why use conventional commits for bug fixes and feature introductions?

Using conventional commits for bug fixes and features ensures structured, machine-readable history. Types like fix and feat clearly communicate the nature of changes, enabling automated changelog generation and semantic versioning.

Can I generate semantic versioning changelogs from conventional commits?

Yes, conventional commits enable semantic versioning and automated changelog generation. By enforcing structured types like feat and fix, this Skill ensures your commit messages are formatted correctly for those downstream automation workflows.