Git Visual Commits

This skill drives the entire git commit workflow — reviewing changes, grouping them logically, composing messages with the right emoji, and only adding a conventional prefix when the user explicitly asks for that combo. It supports three identity modes: bot-attributed (git bot commit), human-attributed (git commit), and collaborative (git our commit).

Critical Rules

Invocation Routing Lock

• An explicit git bot commit, git commit, or git our commit phrase is an authoritative request to use this skill. Do not substitute a changelog, release-note, squash-summary, or generic commit workflow.
• Interpret Please do a git bot commit yolo as git bot commit identity plus auto-approval for the full current worktree. yolo is not the commit message, and it does not request a changelog.
• Equivalent word order and punctuation, such as git bot commit, yolo or yolo — do a git bot commit, preserve the same routing when both the explicit commit command and modifier are present.
• A competing skill may run only when the user also explicitly requests its distinct output, such as updating CHANGELOG.md, drafting release notes, or producing a squash summary.

Full-Skill Read and Subject Lock

Before running any Git command or composing a subject, read this SKILL.md completely from the first line through EOF. A metadata preview, excerpt, cached recollection, or partial read is not sufficient. If a tool truncates the file, continue from the first unread line until EOF before proceeding.