lcp-git-commit

When asked to commit, write clear git commit messages (50/72, present tense, subsystem prefixes like go-lcpd:).

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

When & Why to Use This Skill

This Claude skill automates the generation of professional Git commit messages following the industry-standard 50/72 rule. It ensures repository consistency by enforcing present-tense verbs, subsystem prefixes, and atomic commit structures, which significantly improves codebase maintainability, team collaboration, and version control auditability.

Use Cases

  • Standardizing Team Workflows: Enforce a uniform commit style across a development team to ensure the project history remains readable, professional, and easy to navigate.
  • Enhancing Repository Scanability: Automatically apply subsystem prefixes (e.g., 'docs:', 'api:', 'go-lcpd:') to help developers quickly identify the scope and impact of changes in the git log.
  • Optimizing for Debugging and Bisecting: Maintain a clean git history by creating small, independent commits that support 'git bisect' operations, making it easier to isolate and resolve regressions.
namelcp-git-commit
descriptionWhen asked to commit, write clear git commit messages (50/72, present tense, subsystem prefixes like go-lcpd:).
short-descriptionCraft git commit messages for this repo

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).