What problem does it solve?
Unregulated git commits often skip CHANGELOG updates, leading to incomplete release notes, missing change tracking, and accidental remote pushes that disrupt team development workflows.
Core Features & Use Cases
- Strict pre-commit validation gates: Requires explicit selection of commit-only or commit-and-push mode, scope confirmation, and repository identity verification before any git action is taken.
- Mandatory CHANGELOG enforcement: Automatically requires updates to CHANGELOG.md before every commit, with support for SemVer-compliant release headings for versioned releases.
- Safety guardrails: Blocks destructive git commands (such as hard reset or force push) unless explicitly approved by the user, and prevents cross-repository operations.
- Use Case: Development teams following SDLC workflows can use this skill to ensure every code change has a corresponding changelog entry and no unapproved pushes are sent to remote repositories.
Quick Start
Request the AI to safely commit your current code changes with a corresponding CHANGELOG update, and only push to the remote repository if you explicitly confirm you want to perform the push action.