What is the 50/72 rule enforced by this skill?

It is a standard git practice where the summary line is kept under 50 characters and the body text is wrapped at 72 characters for maximum readability across various git tools.

Does this skill handle LCP-specific subsystem prefixes?

Yes, it automatically identifies and applies prefixes like go-lcpd:, docs:, or apps/openai-serve: to your commit messages based on the files changed.

Can I use this for changes that affect multiple packages?

Absolutely. For broad changes, the skill combines prefixes using a plus sign, such as 'go-lcpd+docs:', to indicate the scope accurately.

Will it prevent me from committing local development files?

Yes, the skill specifically checks for and excludes common local artifacts like go.work.sum to ensure your commits remain clean and production-ready.

Why does the skill insist on present-tense verbs?

Present tense (e.g., 'Fix' instead of 'Fixed') is the industry standard for git commits because it describes what the commit *does* when applied to the codebase.

LCP Git Commit Formatter

Name: LCP Git Commit Formatter
Author: YusukeShimizu

byYusukeShimizu

•

Herramientas de Colaboración

Generates standardized, professionally formatted git commit messages following the Lightning Compute Protocol's specific style guidelines.

Acerca de

This skill ensures that every contribution to the Lightning Compute Protocol (LCP) repository adheres to strict version control standards. It automatically applies the 50/72 rule, enforces present-tense verbs, and identifies appropriate subsystem prefixes like go-lcpd or docs/protocol. By organizing changes into small, logical commits and filtering out development artifacts, it helps maintain a clean, bisect-friendly project history that is easy for teams to review and navigate.

Características Principales

Supports present-tense verb usage for repository consistency
Automatically applies subsystem prefixes like go-lcpd and apps/openai-serve
Enforces the 50/72 character rule for commit summaries and bodies
Filters out local development artifacts and temporary files
Encourages atomic commits to improve git bisect functionality
2 GitHub stars

Casos de Uso

Contributing clean, formatted code to the Lightning Compute Protocol repository
Organizing complex PRs into readable, subsystem-prefixed commits
Maintaining a professional and searchable commit history for LCP-based projects

Acerca de

Características Principales

Supports present-tense verb usage for repository consistency
Automatically applies subsystem prefixes like go-lcpd and apps/openai-serve
Enforces the 50/72 character rule for commit summaries and bodies
Filters out local development artifacts and temporary files
Encourages atomic commits to improve git bisect functionality
2 GitHub stars

Casos de Uso

Contributing clean, formatted code to the Lightning Compute Protocol repository
Organizing complex PRs into readable, subsystem-prefixed commits
Maintaining a professional and searchable commit history for LCP-based projects