commit-all

Stage all working tree changes and create a conventional commit.

Updated Feb 26, 2026

Search Tags:#git #commit #staging #workflow-automation #version-control #conventional-commits

Ready to run

npx skills add https://github.com/heikopanjas/agent-skills --skill commit-all

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-all
Source: https://github.com/heikopanjas/agent-skills/tree/main/commit-all
Command: npx skills add https://github.com/heikopanjas/agent-skills --skill commit-all

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit all current changes to a git repository, using the conventional commits format to ensure consistent messages and traceability.

Core Features & Use Cases

Stage all changes with git add -A before committing, guaranteeing nothing is left behind.
Create a single, unified commit that covers modified, added, and deleted files.
Use when you need a clean, conformant history after completing a feature, bug fix, or cleanup.

Quick Start

Ask the AI to commit all current changes in the repository using a conventional commit message.

Frequently Asked Questions about commit-all

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

FAQPage Schema

How do I commit all changes in git with a conventional commit message?▼

To commit all changes, the skill stages every modification using git add -A and generates a single conventional commit message. This ensures your repository history remains clean and traceable after completing a feature or bug fix.

What is the best way to automate staging and committing all modified and deleted files?▼

Automating this workflow stages all working tree changes, including deleted and modified files, into one unified commit. It applies conventional commit guidelines to format the message, guaranteeing nothing is left behind in your working directory.

Do I need git installed to use a conventional commit workflow automation tool?▼

Yes, git must be installed and available in your system's PATH to use this conventional commit automation. It relies on the underlying git commands to stage all changes and create the final commit in your repository.

Can I create a single conventional commit for both added and deleted files?▼

Yes, a single conventional commit can capture all added, modified, and deleted files. The tool stages all modifications with git add -A before committing, ensuring every change is included in one well-formatted commit message.

When should I avoid committing all working tree changes into a single commit?▼

You should avoid committing all changes into a single commit if your working tree contains unrelated modifications. This workflow is best suited for completing a specific feature, bug fix, or cleanup where a single unified commit accurately represents the changes.