commit

Enforce conventional commit formats and pre-commit checks for Git workflows.

6|2|Updated Jul 8, 2012
One-click install
npx skills add https://github.com/athal7/dotfiles --skill commit-athal7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/athal7/dotfiles/tree/main/skills/commit
Command: npx skills add https://github.com/athal7/dotfiles --skill commit-athal7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Semantic commit formats and strict pre-commit checks are essential to maintain a readable, machine-friendly project history, reduce review friction, and enable automated changelog generation.

Core Features & Use Cases

  • Enforce conventional commits across the team to standardize messages for tooling and release notes.
  • Run pre-commit checks automatically to validate staged changes and enforce policies before every commit.
  • Provide a clear audit trail with standardized trailers (e.g., Co-Authored-By) and consistent history for code reviews.

Quick Start

Draft a conventional commit message for the current staged changes and run the pre-commit checks

Frequently Asked Questions about commit

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

FAQPage Schema
How do I enforce conventional commits across my team's Git workflow?

Enforce conventional commits by validating staged changes with pre-commit checks, standardizing commit messages for tooling, and ensuring consistent history across feature, release, and hotfix branches for automated changelog generation.

What is the best way to automate semantic commit message validation?

Automate semantic commit message validation by applying pre-commit checks that verify staged changes against conventional commit formats and enforce messaging guidelines before every commit is finalized in the repository.

Does this pre-commit check work with feature, release, and hotfix branches?

Yes, the pre-commit checks apply to software development workflows across feature, release, and hotfix branches, verifying staged changes and enforcing consistent policies and automated messaging guidelines throughout the project.

How do I add standardized trailers like Co-Authored-By to my Git commits?

Add standardized collaboration trailers like Co-Authored-By through automated pre-commit checks that append metadata to semantic commit messages, providing a clear audit trail for code reviews and project history.

Why use semantic commit formats for automated code reviews?

Semantic commit formats maintain a readable, machine-friendly project history that reduces review friction and enables automated changelog generation, satisfying requirements for staged-change verification and consistent messaging guidelines.