juanibiapina/dotfiles/commit

Commit

Commit only when the user asks.

Review the uncommitted changes and recent commit style. Load the documentation skill and write the message by its rules. Commit only the changes that belong to the request.

Always use GitButler. Load the but skill and commit with but directly. Commit to a new branch named after the ticket if one exists (e.g. PROJ-123-short-description), otherwise after the change. Put later commits for the same task on the branch the session already created.

When a but command fails with Setup required, run but setup, tell the user the repository was converted, and retry the command. Setup keeps the current branch and uncommitted changes.

Amend an unpublished local commit when a small fix clearly belongs with that commit's intent. Ask before rewriting pushed, reviewed, or shared history.

Guardrails

• Push or force push only when the user asks.
• Use non-interactive commands; no terminal is attached to answer prompts.
• Run destructive commands (reset --hard, clean, branch -D, but discard) only on request.
• Leave out files that likely hold secrets, and skip empty commits.