commit-push-with-changelog

Enforces CHANGELOG.md updates and confirms pushes before executing git commits.

Updated May 27, 2026
One-click install
npx skills add https://github.com/santanapol/agent-skills --skill commit-push-with-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-push-with-changelog
Source: https://github.com/santanapol/agent-skills/tree/main/.cursor/skills/commit-push-with-changelog
Command: npx skills add https://github.com/santanapol/agent-skills --skill commit-push-with-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about commit-push-with-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce a CHANGELOG update before every git commit?

You can enforce a CHANGELOG update before every git commit by applying strict pre-commit validation gates that block the commit unless CHANGELOG.md is modified. This skill requires mandatory changelog edits and SemVer-compliant release headings before allowing any repository commits.

How can I prevent accidental git pushes to remote repositories?

To prevent accidental git pushes, you can require explicit user confirmation before executing any remote actions. This skill separates commit-only and commit-and-push modes, demanding explicit scope confirmation and repository identity verification before sending updates to remote repositories.

How do I block destructive git commands like hard reset or force push?

You can block destructive git commands like hard reset or force push by implementing safety guardrails that require explicit user approval. This skill prevents destructive git actions and cross-repository operations unless explicitly confirmed by the user.

What is the safest way to sync SemVer release notes with version control?

The safest way to sync SemVer release notes with version control is to strictly couple changelog modifications with commit operations. This skill enforces mandatory pre-commit CHANGELOG.md updates with SemVer-compliant release heading formatting for versioned releases.

Does this git safety workflow require external dependencies or tools?

No, this git safety workflow does not require external dependencies. It operates independently to apply pre-commit validation gates, mandatory changelog enforcement, and safety guardrails for version control operations without relying on additional tools or libraries.