What problem does it solve? Code changes made without version control discipline become impossible to review, revert, or release safely. This Skill enforces structured git workflows—atomic commits, short-lived branches, semantic versioning, and curated changelogs—so every change stays manageable and every release communicates clearly to consumers. ## Core Features & Use Cases - Commit Discipline: Enforces atomic commits with conventional message types (feat, fix, refactor, test, docs, chore) and pre-commit hygiene checks for secrets, tests, and linting. - Branching & Parallel Work: Guides trunk-based development with short-lived feature branches and git worktrees for running parallel work streams without interference. - Release & Versioning: Applies semantic versioning rules (MAJOR.MINOR.PATCH), annotated git tags as the source of truth, and human-readable changelogs grouped by impact. - Use Case: When finishing a feature, use this Skill to split the work into atomic commits, verify no secrets are staged, choose the correct version bump, tag the release, and write the changelog entry. ## Quick Start Review my current uncommitted changes and help me split them into atomic commits with proper messages, then advise on the right semantic version bump for the release.
