Claude-skill-registry lcp-git-commit

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

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/lcp-git-commit" ~/.claude/skills/majiayu000-claude-skill-registry-lcp-git-commit && rm -rf "$T"

manifest: skills/data/lcp-git-commit/SKILL.md

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

Confirm which files belong in the commit (avoid committing local/dev artifacts like
```
go.work.sum
```
).
Craft a commit message following the style above.
Create the commit(s) with clear boundaries (one topic per commit when practical).