writing-commit-messages

Draft a Git commit message from the staged or working-tree diff
Identify the correct subsystem prefix from changed file paths and produce a lowercase, imperative subject line under 60 characters

A formatted commit message with subsystem-prefixed subject, optional references, and a long-form description
The applied commit in the local repository (not pushed)

Does not push commits; that is left to the user
Subject lines should ideally be under 60 characters total
Subject line uses a lowercase subsystem prefix derived from the changed file paths (e.g., terminal, vt, lib, config, font, macos, gtk, build)
Subject line starts lowercase, uses imperative mood, and has no trailing period
References section is omitted entirely with no blank line when no GitHub issues, PRs, or discussions apply
Long-form description uses plain prose rather than bullet points and is wrapped at approximately 72 characters

AI 搜索