What problem does it solve? Writing consistent, complete commit messages and changelog entries across Getty repositories is error-prone: vague summaries, missing file-level changes, duplicated changelog bullets, and accidental @ mentions or wrong issue references all slip in. This Skill enforces a strict format so every commit and Changes entry follows the same rules. ## Core Features & Use Cases - Commit message formatting: imperative summary line (max ~72 chars), one body line per discrete change, no filler phrases, and a Co-Authored-By trailer naming the actual model. - Changelog discipline: one topic per entry, rewrite existing unreleased bullets instead of appending, describe the destination not the journey, and reference only publicly readable trackers. - Multi-repo and HEREDOC handling: separate commits per repo without cross-references, and messages passed via HEREDOC to preserve formatting. - Use Case: After renaming an accessor across three Perl modules, produce a commit message listing every touched file and update the unreleased Changes section in the same commit. ## Quick Start Write a commit message for my staged changes following the Getty commit style, including the changelog entry.
