skills.rest
nickcorin
nickcorinCOMMUNITY
Explore all skills by this author →
𝕏@maxxedgoofGitHub

git-commit

Enforce standardized git commit messages with package names and first-line rules.

2|Updated Feb 27, 2020
Search Tags:#automation#git#commit#conventions#policies#version-control#commit-message
One-click install
npx skills add https://github.com/nickcorin/dotfiles --skill git-commit-nickcorin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/nickcorin/dotfiles/tree/main/dot_config/opencode/skill/git-commit
Command: npx skills add https://github.com/nickcorin/dotfiles --skill git-commit-nickcorin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create consistent git commits across a codebase, reducing ambiguity and making history easier to review.

Core Features & Use Cases

  • Enforces a standardized commit format that includes a package name and a concise summary.
  • Validates first-line rules (not optional, not starting with capital, not a complete sentence) and optional detailed body constraints.
  • Use case: when preparing to commit changes to a git branch, ensure messages follow the project's conventions and link relevant references when needed.

Quick Start

Ask me to generate a commit message using the required format for a given package and summary.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I standardize git commit messages across multi-module repos?▼

Standardize git commit messages by enforcing a strict format that includes a package name and a concise summary. This applies during code changes commit preparation across software development workflows, including multi-module repos and feature branches, reducing ambiguity.

What rules should a git commit message first line follow?▼

Git commit message first-line rules enforce that the line is not optional, does not start with a capital, and is not a complete sentence. This ensures consistently clear, concise summaries across a codebase.

How do I generate a commit message with package name inclusion and optional references?▼

Generate a commit message using the required format by providing a given package and summary. The schema enforces package name inclusion and allows linking relevant optional references when needed during preparation.

Does this commit convention tool work with feature branches?▼

Yes, this commit convention tool works with feature branches. It applies during code changes commit preparation across software development workflows, ensuring messages follow project conventions on any branch.

Why enforce strict commit message policies in version control?▼

Enforce strict commit message policies in version control to reduce ambiguity and make history easier to review. Validating first-line rules and optional detailed body constraints creates consistently clear git commits.

Related Skills

Explore More Software Engineering Skills→
zaziedlmzaziedlm

pr-draft-summary

Generate PR-ready titles and descriptions from git diffs and commit history.

Community
Intermediate
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic
fengqiyu0317fengqiyu0317

commit-msg

Format git commit messages with structured tags, file paths, and descriptions.

Community
Basic
krisssskrissss

git-commit

Generate standardized Git commit messages following project conventions and Conventional Commits.

Community
Intermediate