crafting-commits

Automatically invoked when user requests git commit message creation, commit drafting, or needs help with conventional commit formatting. Handles conventional commit standards.

⭐5stars🔀0forks📁View on GitHub🕐Updated Jan 1, 2026⬇️2downloads

When & Why to Use This Skill

The Crafting Commits skill automates the creation of professional Git commit messages by analyzing staged changes and adhering to conventional commit standards. It streamlines the development workflow by ensuring consistent formatting, providing collaborative attribution, and performing quality validation to maintain a clean, readable, and searchable project history.

Use Cases

  • Automated Commit Drafting: Quickly generate descriptive and structured commit messages based on staged changes to save time and maintain high-quality documentation.
  • Standardizing Team Workflows: Enforce Conventional Commit standards across a repository to facilitate automated changelog generation and semantic versioning.
  • Collaborative Attribution: Automatically include 'Co-Authored-By' trailers in commit messages to ensure proper credit during pair programming or multi-contributor sessions.
  • Commit Quality Validation: Use integrated scripts to verify that commit messages meet professional standards and formatting requirements before they are finalized.
  • Context-Aware Analysis: Analyze git status and diffs to identify the scope and impact of changes, including the detection of breaking changes for better release management.
namecrafting-commits
descriptionGenerates git commit messages following conventional commit standards with collaborative attribution. Use when user requests commit message creation, drafting, or help with formatting.
- bash(git*)

Crafting Git Commits

A professional git commit message drafting service that follows modern conventional commit standards, provides collaborative attribution, and includes quality validation for reliable development workflows.

This skill follows the principle of progressive disclosure. This file contains the core workflow and high-level guidance. For more detailed information, please refer to the linked reference files.

Core Workflow

  1. Analysis: I start by analyzing the staged changes to understand the context.
    • git status
    • git diff --staged
    • git log --oneline -5
  2. Planning: I identify the commit type, scope, and assess any potential impact, including breaking changes.
  3. Validation: I use a detailed checklist to ensure the commit message meets all quality standards. See validation.md for the full checklist.
  4. Execution: I draft the commit message, add attribution, and execute the commit, verifying it in the git history.

Reference Documents

For detailed information, please refer to these files:

  • examples.md: A comprehensive list of commit message examples for different scenarios (features, bug fixes, docs, etc.).
  • validation.md: Detailed checklists for validating commits at all freedom levels.
  • patterns.md: Advanced patterns, formatting best practices, attribution guidelines, and freedom levels.
  • troubleshooting.md: A guide to common Git errors and recovery procedures.

Utility Scripts

This skill includes executable scripts for validation and analysis.

  • scripts/validate_commit.sh: Checks if a commit message follows the conventional commit format.
  • scripts/check_attribution.sh: Validates the Co-Authored-By format in a commit message.
  • scripts/analyze_changes.sh: Provides a summary of staged changes to help draft a commit message.

System Requirements

  • Git version 2.25.0 or higher
  • Bash shell access
  • Standard Unix tools (ls, grep, etc.)