commit

Tidy changes, update CHANGELOG.md, and create a git commit.

69|12|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/gtapps/claude-code-hermit --skill commit-gtapps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/gtapps/claude-code-hermit/tree/main/plugins/claude-code-dev-hermit/.claude/skills/commit
Command: npx skills add https://github.com/gtapps/claude-code-hermit --skill commit-gtapps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the day-to-day commit workflow for plugin development, reducing manual steps by tidying changes, appending a changelog line, and creating a clean commit.

Core Features & Use Cases

  • Tidy changes before committing to ensure a clean working tree.
  • Append an entry to CHANGELOG.md under the Unreleased section.
  • Draft and propose a concise, imperative commit message and perform the commit after user approval.
  • Guard against unsafe operations like pushes/tags and detect secrets or large binaries before committing.

Quick Start

Instruct the agent to tidy the changes, update the changelog, and commit.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate updating a changelog and creating a git commit?

You can automate updating a changelog and creating a git commit by using a workflow that reviews diffs, appends an entry to CHANGELOG.md under the Unreleased section, drafts a concise commit message, and executes the commit after your approval.

Can I automatically tidy code changes before committing to git?

Yes, you can tidy code changes before committing to git. The workflow specifically tidies changes to ensure a clean working tree before proceeding with the changelog update and commit creation.

Does the commit workflow check for secrets or large files before committing?

The commit workflow does check for secrets or large files before committing. It enforces guardrails by reviewing diffs to detect secrets or large binaries, ensuring unsafe operations are avoided before finalizing the commit.

What is the best way to generate a concise git commit message for plugin development?

The best way to generate a concise git commit message for plugin development is to use an automated workflow that drafts an imperative commit message based on the reviewed code diffs and changelog updates, proposing it for your approval.

Are there limitations on pushing or tagging when using an automated git commit workflow?

There are limitations on pushing or tagging when using an automated git commit workflow. The guardrails specifically disallow pushes and tags, as well as other unsafe operations, restricting the scope to local commits only.