commit

Create atomic Conventional Commits from in-scope working tree files.

Updated Jul 10, 2026

Search Tags:#code quality #git #commit #conventional commits #atomic commits

Ready to run

npx skills add https://github.com/acme-skunkworks/changelog-core --skill commit-acme-skunkworks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/acme-skunkworks/changelog-core/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/acme-skunkworks/changelog-core --skill commit-acme-skunkworks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers manage their working tree by transforming uncommitted changes into well-structured, atomic commits, ensuring code quality and maintaining a clean branch history.

Core Features & Use Cases

Conventional Commits: Generates Conventional Commits following the semantic commit message guidelines.
Scope Guard: Classifies files as in-scope or out-of-scope based on the branch's merge base, preventing accidental commits of unrelated files.
Atomic Commits: Ensures each commit represents a single, coherent change, reducing complexity and improving maintainability.
Use Case: Before merging a feature branch, use this Skill to commit all changes in a structured manner, ensuring that only relevant code is included in the final commit.

Quick Start

Use the commit skill to create atomic commits for your changes in the current branch.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I create atomic commits from my current working tree?▼

This Skill creates atomic commits by analyzing your working tree's in-scope files against a specified branch's merge base. It ensures each commit represents a single coherent change, reducing complexity and improving branch history maintainability.

What are conventional commits and how are they generated?▼

Conventional commits follow semantic commit message guidelines for clear history. This Skill automatically generates conventional commit messages by analyzing your working tree changes, ensuring code quality and well-structured branch history before merging a feature branch.

How do I prevent accidental commits of unrelated files in my git branch?▼

This Skill provides a scope guard that classifies files as in-scope or out-of-scope based on the branch's merge base. This prevents accidental commits of unrelated files, ensuring only relevant code changes are included in your final structured commit.

Do I need the git CLI installed to structure my uncommitted changes into logical commits?▼

Yes, you need the git CLI installed to use this Skill. It requires the git CLI for status and diff analysis to evaluate your working tree and to create the final logical, atomic commits on your branch.

When should I use an atomic commit workflow for my feature branch?▼

You should use an atomic commit workflow before merging a feature branch to ensure your changes are well-structured. This approach guarantees each commit represents a single coherent change, maintaining code quality and a clean branch history.