# Lcp Git Commit > When asked to commit, write clear git commit messages (50/72, present tense, subsystem prefixes like go-lcpd:). Use when this capability is needed. - Skill: `tomevault-io/lcp-git-commit` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/lcp-git-commit` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/lcp-git-commit/raw - Safety review: pending - 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/lcp-git-commit --- Use this skill only when the user explicitly asks you to create commits. ## Commit message style Follow this structure: - First line: short summary (aim for 50 chars or less). - Blank line. - Body (optional): wrap at ~72 columns; explain intent and rationale. Guidelines: - Use present tense (example: “Fix …”, not “Fixed …”). - Include a subsystem/package prefix when it improves scanability: - Examples: `go-lcpd: …`, `apps/openai-serve: …`, `docs: …`, `docs/protocol: …` - For broad changes, combine prefixes with `+` (example: `go-lcpd+docs: …`). - Prefer small, contained commits that build independently to support `git bisect`. - Bullets are fine in the body; keep them readable and wrapped. ## When asked to commit 1. Confirm which files belong in the commit (avoid committing local/dev artifacts like `go.work.sum`). 2. Craft a commit message following the style above. 3. Create the commit(s) with clear boundaries (one topic per commit when practical). --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/yusukeshimizu) — claim your Tome and manage your conversions.