Commit

Scope

• Use (debian) when the change is specific to the Debian/GNOME/Wayland migration or GNOME-only config
• Omit the scope when the change is general or applies across all machines
• Other scopes are fine if they clearly describe a platform or area (e.g., (ssh), (git))

Description

• Lowercase, no period at the end
• Short and action-oriented — describe what changed, not why
• Start with a noun or the thing being changed (e.g., "bringme.sh window matching", "alt-tab to current workspace only")

Rules

1. If no files are staged, stage all modified and new files automatically
2. Do NOT split into multiple commits — dotfiles changes are typically one logical unit
3. Do NOT add a commit body unless the user specifically asks for one
4. Do NOT run pre-commit checks — there are none in this repo
5. Do NOT push unless the user asks — just commit
6. Always review the diff to pick the right verb and scope
7. Do NOT add a Co-Authored-By line or any AI attribution to the commit message

Examples

From this repo's history:

add(debian): swappy screenshot+annotate workflow replacing flameshot on Wayland
update(debian): bringme.sh and move-to-workspace.sh to use window-tools D-Bus extension
fix(debian): use chezmoi.homeDir template for GNOME shortcut paths
cut(debian): remove tools not available on debian