# Regjit Git Commit > Use when preparing to commit code changes, ensuring clear messages and proper git workflow for RegJIT project - Skill: `tomevault-io/regjit-git-commit` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/regjit-git-commit` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/regjit-git-commit/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/regjit-git-commit --- # RegJIT Git Commit Workflow ## Overview Write clear, meaningful git commits that document code changes effectively and maintain project history for future developers. ## When to Use - After completing a feature - After fixing a bug - After writing tests - Before pushing changes - When preparing pull requests - During code review ## Commit Message Format Follow **Conventional Commits** with semantic versioning: ``` ():