commit

Consolidate all tracked and untracked changes into a single conventional commit.

Updated Feb 11, 2016

Search Tags:#git #workflow #commit #version-control #conventional-commits #scopes #safe-commit

Ready to run

npx skills add https://github.com/Ehrax/dotfiles --skill commit-ehrax

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Ehrax/dotfiles/tree/main/configs/agents/skills/commit
Command: npx skills add https://github.com/Ehrax/dotfiles --skill commit-ehrax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit all current changes as a single conventional commit to simplify version control history and improve traceability.

Core Features & Use Cases

Enforces conventional commit messages (feat, fix, docs, chore, refactor, test, build, ci, perf, style, revert).
Encourages an optional scope for clear intent (feat(auth): ...).
Provides a reliable, one-shot workflow to commit both tracked and untracked changes quickly and safely.

Quick Start

Create a single conventional commit that includes all current changes.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I commit all tracked and untracked changes as a single conventional commit?▼

To commit all changes as a single conventional commit, the Skill inspects git status, diff, and log, stages all tracked and untracked files, and creates one safe commit to ensure a clean, readable history.

What are conventional commit types and scopes for git version control?▼

Conventional commit types include feat, fix, docs, chore, refactor, test, build, ci, perf, style, and revert. Scopes are optional labels like auth that provide clear intent for the changes within your version-control workflow.

How do I stage all files and generate a conventional commit message automatically?▼

You can stage all files and generate a conventional commit message by running this Skill. It inspects your repository diff and log to consolidate all current changes into a single, consistently formatted commit.

Can I use this safe-commit workflow for large git repositories?▼

Yes, this safe-commit workflow is useful for committing both tracked and untracked changes across small to large repositories, providing a reliable, one-shot process to consolidate all changes quickly and safely.

Why consolidate all current changes into one git commit instead of multiple commits?▼

Consolidating all current changes into one git commit simplifies version control history and improves traceability. It enforces consistent messaging and ensures the final repository state remains clean and readable.

Does this git commit process verify the final repository state after staging?▼

Yes, the git commit process verifies the final repository state. After it stages all changes and enforces the conventional commit type with an optional scope, it inspects the repository to confirm a safe commit.