What problem does it solve?
This skill governs the execution of a commit when the user requests to save vibe-coding changes, deciding which files belong in the commit, excluding generated or unwanted changes, and handling multi-line messages and trailers.
Core Features & Use Cases
- Decide the exact files and hunks to include in a commit from a dirty working tree, ensuring a single coherent changeset.
- Stage only the intended changes, exclude noise and generated artifacts, and verify the staged set before committing.
- Manage commit messages and trailers safely, preserving history boundaries and avoiding unintended rewrites or pushes.
- Enforce safety and workflow boundaries: do not push unless explicitly asked, and avoid mutating shared history.
Quick Start
Review the current changes, decide the exact file set for the commit, stage only the selected hunks, verify the staged set, and compose a safe commit message with trailers.