commit

Create a conventional commit using chez_commit. Use when the user asks to commit changes. Do not EVER use

⭐4stars🔀0forks📁View on GitHub🕐Updated Jan 8, 2026

When & Why to Use This Skill

This Claude skill streamlines the version control process by generating standardized Git commits following the Conventional Commits specification. By utilizing the chez_commit tool, it automates file staging and message formatting with professional tags like feat, fix, ref, and chore, ensuring a clean, searchable, and industry-standard project history.

Use Cases

  • Automating standardized commits: Quickly generate Git commits that follow the Conventional Commits standard to maintain a professional project log.
  • Streamlining development workflows: Stage specific files and commit changes in a single command based on natural language descriptions of the work performed.
  • Enhancing repository readability: Ensure every code change is categorized correctly (e.g., distinguishing between a 'fix' and a 'refactor') to simplify future debugging and changelog generation.
  • Professionalizing AI-assisted coding: Create human-like commit messages that integrate seamlessly into team environments without mentioning AI involvement.
namecommit
descriptionCreate a conventional commit using chez_commit. Use when the user asks to commit changes. Do not EVER use

Create a commit using chez_commit, which stages the specified files and commits them.

Usage

chez_commit ...

Valid Tags (in order of preference)

  1. feat - New feature, feature improvement, or feature removal
  2. fix - User-facing bug fix (not linting errors unless they caught a real bug)
  3. ref - Refactor/restructure production code without changing external behavior. IMPORTANT: Only use 'ref' when there are ZERO user-facing changes. If users would notice any difference in behavior, use 'feat' or 'fix' instead.
  4. chore - Other changes (build scripts, CI/CD, deps, linting, formatting, documentation) not modifying production code

Instructions

  1. Run chez_commit <tag> "<message>" <file>...
  2. The specified files will be staged automatically
  3. The message can contain newlines for multi-line commits
  4. NEVER mention "Claude" or "Claude Code" in commit messages - write as if a human authored the commit

Example

chez_commit feat "Add user authentication

This adds login and logout functionality." src/auth.py src/login.py