skills.rest
YusukeShimizu
YusukeShimizuCOMMUNITY
Explore all skills by this author →
GitHub

lcp-git-commit

Generate git commit messages with 50-character subjects and 72-column bodies.

2|Updated Dec 30, 2025
Search Tags:#coding-standards#version-control#prefixes#commit-messages#git-commit#present-tense
One-click install
npx skills add https://github.com/YusukeShimizu/lightning-compute-protocol --skill lcp-git-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lcp-git-commit
Source: https://github.com/YusukeShimizu/lightning-compute-protocol/tree/main/.codex/skills/lcp-git-commit
Command: npx skills add https://github.com/YusukeShimizu/lightning-compute-protocol --skill lcp-git-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps ensure consistent, readable git commit messages across a project, improving traceability for teammates and future maintenance.

Core Features & Use Cases

  • Structured Commit Messages: Enforces subject lines around 50 characters and body wrapping around 72 characters.
  • Present Tense & Prefixes: Applies present-tense verbs and supports subsystem prefixes like go-lcpd:.
  • Use Case: When documenting a small bug fix or code refactor, generate a concise commit that clearly describes the change and its scope.

Quick Start

Prompt: Create a commit message for a bug fix in the lcpd module that follows the style guide.

Frequently Asked Questions about lcp-git-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write git commit messages that follow a consistent style guide?▼

Git commit messages should enforce a subject line around 50 characters and wrap the body at 72 columns. Using present-tense phrasing and subsystem prefixes ensures a structured, readable project history.

What is the best way to format git commit subjects and bodies for traceability?▼

Formatting git commits involves keeping subjects near 50 characters and wrapping bodies at 72 columns. Adding subsystem prefixes like go-lcpd: improves traceability and clearly defines the change scope for teammates.

How do I generate a commit message for a bug fix or code refactor?▼

Generate commit messages for bug fixes or refactors by applying present-tense verbs and optional subsystem prefixes. This structured approach ensures the change and its scope are clearly documented for future maintenance.

Do I need a specific git workflow to use present-tense commit prefixes?▼

No specific git workflow is required. You only need to apply present-tense verbs and optional subsystem prefixes like go-lcpd: to your commit messages, ensuring they fit the 50-character subject and 72-column body limits.

Can I add subsystem prefixes like go-lcpd: to my git commit messages?▼

Yes, you can add subsystem prefixes like go-lcpd: to your git commit messages. This skill supports applying these prefixes alongside present-tense verbs to maintain a consistent and readable version control history.

Why does my git commit history lack consistent structure across different modules?▼

Git commit history lacks structure without enforced rules. Applying a strict style guide with 50-character subjects, 72-column body wrapping, and present-tense phrasing resolves this by ensuring readable, traceable commits.

Related Skills

Explore More Software Engineering Skills→
mgoodman60mgoodman60

commit

Generate descriptive Git commit messages from repository changes with conventional formatting.

Community
Basic
mattg101mattg101
1

gcp-copy

Stage all changes, commit with a message, and push to a remote Git repository.

Community
Basic
SoundBlasterSoundBlaster
20

flow-primitive-commit

Create task-scoped commits by staging only relevant files with present-tense messages.

Community
Intermediate
Awish021Awish021
10

conventional-commits

Generate Git commit messages adhering to the Conventional Commits specification.

Community
Basic