What problem does it solve? Writing good commit messages and deciding whether to stack or squash changes is repetitive and error-prone. This Skill inspects your working tree, proposes a commit message based on the actual diff, and creates the commit through a single confirmation dialog — without ever pushing. ## Core Features & Use Cases - Repository Analysis: Runs a script that reports git status, unpushed commits, staged and unstaged diffs, untracked files, and recent commit style for message reference. - Stack or Squash: When unpushed commits exist, one dialog lets you commit on top, squash into the last commit via --amend, or reword the proposed message. - Safety Guardrails: Staging script warns about sensitive files (.env, .pem, .key) and the commit script rejects any AI attribution in messages. - Use Case: You finished a feature with several modified files and one unpushed commit. Invoke the skill, review the proposed message, choose "Squash into the last commit", and the changes are amended in — nothing is pushed. ## Quick Start Ask the assistant to commit your current changes, for example by saying "commit my changes but don't push".
