commit

Create Git commits following the Conventional Commits specification.

15|5|Updated Jul 1, 2025

Search Tags:#git #workflow #code review #version control #commit #conventional commits

Ready to run

npx skills add https://github.com/swissarmyhammer/swissarmyhammer --skill commit-swissarmyhammer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/swissarmyhammer/swissarmyhammer/tree/main/builtin/skills/commit
Command: npx skills add https://github.com/swissarmyhammer/swissarmyhammer --skill commit-swissarmyhammer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating well-formatted Git commits, ensuring code changes are properly documented and adhere to project standards.

Core Features & Use Cases

Conventional Commits: Automatically generates commits following the Conventional Commits specification for better changelog generation and semantic versioning.
File Staging: Intelligently identifies and stages all modified and new source files, preventing missed changes.
Use Case: After completing a new feature, use this skill to commit your code with a clear, descriptive message like "feat: Add user authentication via OAuth2".

Quick Start

Use the commit skill to save your current changes with a conventional commit message.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I automate git commits to follow the Conventional Commits specification?▼

This Skill automates creating git commits following the Conventional Commits specification. It intelligently stages all modified and new source files while enforcing project-specific git practices to generate consistent, well-documented version control check-ins.

What is the best way to stage all modified files and generate a conventional commit message?▼

The best way to stage modified files and generate a conventional commit message is using this Skill. It identifies and stages all new and updated source files comprehensively, then enforces project-specific git practices to ensure consistent semantic versioning check-ins.

How does Conventional Commits formatting improve code review and version control?▼

Conventional Commits formatting improves version control by standardizing commit messages with clear prefixes like 'feat' or 'fix'. This consistency enables better changelog generation, clear semantic versioning, and streamlined code review tracking across project history.

Do I need to manually stage new source files before creating a conventional commit?▼

You do not need to manually stage new source files before creating a conventional commit. The process automatically identifies and manages the staging of all modified and new source files, preventing missed changes and ensuring comprehensive code check-ins.

Can I enforce project-specific git practices when generating commit messages?▼

Yes, you can enforce project-specific git practices when generating commit messages. The automation ensures that all created commits adhere to your specific coding standards and Conventional Commits specifications, maintaining consistent version control across the project.

Why use Conventional Commits for automated code check-ins and changelog generation?▼

Using Conventional Commits for automated code check-ins provides structured, descriptive messages like 'feat: Add user authentication'. This standardization directly supports automated changelog generation and semantic versioning while preventing missed source file changes.