# Commit > Optionally checks, then commits code to the current or a new feature branch. Use when this capability is needed. - Skill: `tomevault-io/commit-47` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/commit-47` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/commit-47/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-47 --- When asked to commit code, follow these steps: ## Arguments - `check` (default): Run checks first to lint, build, and test the code. Stop if any checks fail. - `force`: Skip the check step and commit directly. ## Steps 1. Run these bash commands in parallel to understand the current state: - `git status` to see all untracked files - `git diff HEAD` to see both staged and unstaged changes - `git log --oneline -10` to see recent commit messages for style consistency 2. If you are on the `main` branch, create a new feature branch using `git branch` and switch to it. 3. Analyze all changes and draft a commit message: - Summarize the nature of the changes (new feature, enhancement, bug fix, refactoring, test, docs, etc.) - Use the conventional commit format: `type(scope): description` - Keep the first line under 72 characters - Do not commit files that likely contain secrets (.env, credentials.json, etc.) 4. Stage and commit the changes: - Add relevant files using `git add` - Use a plain string for the commit message (do not use HEREDOCs). 5. Report the results including: - The commit hash - The commit message --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/metamask) — claim your Tome and manage your conversions.