commit-changes

Create atomic git commits using conventional commit formatting.

1|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/fusupo/escapement --skill commit-changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-changes
Source: https://github.com/fusupo/escapement/tree/main/skills/commit-changes
Command: npx skills add https://github.com/fusupo/escapement --skill commit-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers to create meaningful, atomic commits that follow a conventional-commit format, improving changelogs and review efficiency.

Core Features & Use Cases

  • Atomic commits: ensure each commit represents a single logical change.
  • Conventional-commit formatting: auto-applies scope and type based on project conventions.
  • Automated prompts: asks which changes to include when multiple logical changes are detected.
  • Project context awareness: reads CLAUDE.md for module emojis and naming conventions to craft consistent messages.

Quick Start

After completing a scratchpad task, say "commit these changes" to trigger the commit workflow and generate a well-formed, atomic commit message.

Frequently Asked Questions about commit-changes

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

FAQPage Schema
How do I create atomic conventional commits automatically?

To create atomic conventional commits automatically, this Skill analyzes your current git state and groups changes into individual logical commits, formatting messages with the correct type and scope rules without manual effort.

What are atomic commits and when do I need them in version control?

Atomic commits ensure each git commit represents a single logical change. You need them in version control to improve changelog accuracy, simplify code review efficiency, and keep the project history clean.

How do I group multiple staged changes into separate git commits?

You can group multiple changes into separate git commits by triggering the workflow; the Skill detects multiple logical changes and prompts you to confirm or adjust which changes to include before finalizing each atomic commit.

Can I use custom naming conventions for conventional commit messages?

Yes, you can use custom naming conventions for conventional commit messages by defining module emojis and naming rules in your CLAUDE.md file, which the Skill reads to craft context-aware messages.

What's the best way to format git commit messages for a changelog?

The best way to format git commit messages for a changelog is using the conventional commits format, which this Skill auto-applies by enforcing scope and type rules based on your project conventions.