git-commiter

Git Commiter

This skill governs every git commit produced in this repository. The project enforces an emoji-prefixed subject line on all commits, a structured commit body, and a per-file commit policy when several unrelated files change together. Read the entire skill before staging or committing, even for a single-line change. Never invent emoji or commit grammar that is not documented here.

Getting Started

1. Run git status --short to enumerate the working-tree changes - never commit blindly.
2. Run git diff --stat (and git diff <file> for each file) to understand what actually changed.
3. Decide the commit topology: one focused commit, or one commit per logically independent file.
4. Pick the correct emoji + Conventional Commit type for each commit (see the vocabulary table below).
5. Write the message to a temp file under .git/ and commit with git commit -F <file> to avoid shell-quoting issues.
6. Always append the mandatory Co-authored-by: Copilot trailer unless the user explicitly opts out.

Never skip reading this skill, even for a one-line change.

The commit subject is a single line ≤ 72 characters built from three parts in this exact order:

<emoji>[<emoji>...] <type>(<scope>): <imperative summary>

• <emoji> (mandatory) - one or more glyphs from the vocabulary table. Multiple glyphs are concatenated with no separator (e.g. ✨🤖, 🛠️🚧, 🐛🛠️).
• <type>(<scope>) (recommended) - Conventional Commit type (feat, fix, refactor, docs, test, chore, ci, build, perf, style) and an optional parenthesised scope (tests, agents, skills, cli, remote).
• <imperative summary> (mandatory) - lowercase, imperative mood ("add", "fix", "remove" - not "added", "fixes"). No trailing period.

Subject must be on line 1, followed by one blank line, followed by the optional body. Never put the body on line 2.

Use only the glyphs in this table. They mirror the existing repository history and must not be substituted with similar Unicode lookalikes.

Pair emoji freely when both apply: ✨🤖 (new agent file is an automation asset), 🐛🛠️ (a bugfix that is also a refactor), ✨🚧 (new but incomplete scaffold), 💣🚧 (refactor still in flight). Always put the primary intent emoji first.

Whenever the diff is more than a trivial typo, write a structured body using the four-section template below. Each section heading is followed by an underline of three dashes (matches existing project history). Keep lines wrapped to ~72 columns.

When the working tree contains multiple unrelated changes, split them into separate commits - one per logically independent file or feature. Stage explicitly with git add <file>; never use git add -A or git add . for a multi-file change. The reviewer must be able to revert any one commit without collateral damage.

Group changes into a single commit only when they form one atomic unit (e.g. a test file plus the fixture it depends on, or a feature plus the docs that describe it).

Before writing any commit message, follow this exact sequence:

Because Windows shells (PowerShell, cmd) mangle multi-line strings and emoji glyphs, always write the commit message to a temporary file under .git/ and pass it via -F. Never use git commit -m "..." for non-trivial messages.

The project's existing history is the canonical reference. The commits below are exemplary - copy their shape, never their content verbatim.

The repository ships a pre-commit hook that may rewrite the commit SHA and prepend additional emoji to the subject (e.g. transforming feat(...) into ✨🤖 feat(...)). This is expected. Always inspect the final subject with git log --oneline -1 after committing to confirm the result, and never re-amend solely to "fix" hook-injected emoji.

• Never commit without an emoji prefix - this is mandatory in every commit on every branch.
• Never use git add -A / git add . when several unrelated files are dirty.
• Never use git commit -m for a multi-line / structured body on Windows.
• Never paste emoji from a thesaurus - use only the glyphs in the vocabulary table.
• Never omit the Co-authored-by: Copilot trailer unless the user explicitly says "no co-author".
• Never write past-tense or third-person subjects ("added", "fixes") - always imperative ("add", "fix").
• Never include a trailing period on the subject line.
• Never exceed 72 characters on the subject; wrap body at ~72.

Before invoking git commit, tick every box: