# Commit > Use when working with the recommended way to commit code to the repository - Skill: `tomevault-io/commit-42` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/commit-42` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/commit-42/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/commit-42 --- # Committing Code to the Repository ## Committing Changes When committing staged changes in Git: - Use Conventional Commits for writing commit messages. Check [the Conventional Commits specification](https://www.conventionalcommits.org/) for details. - Use bullet points for the commit details - If there are bullet points, keep them short and simple - The commit message should be based on the staged changes, not on the recent prompts --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/screenly) — claim your Tome and manage your conversions.