commit

Stage all changes and create conventional commits in Git repositories.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/api-haus/my-claude-workflow --skill commit-api-haus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/api-haus/my-claude-workflow/tree/main/skills/commit
Command: npx skills add https://github.com/api-haus/my-claude-workflow --skill commit-api-haus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit across the repository by staging everything, including untracked files, and creating a clean, conventional commit history.

Core Features & Use Cases

  • Stage all changes, including untracked files
  • Enforce conventional commit messages for consistent history
  • Support worktrees and multi-repo workflows

Quick Start

Stage all changes, including untracked files, and commit with a conventional message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I stage all untracked files and commit them with a conventional commit message?

To stage untracked files and create a conventional commit, you need to configure a Git repository with a conventional-commit style guide. The automation applies the policy automatically, staging all changes and generating a clean, reproducible history across projects.

Can I automate git commits across multi-repo worktrees?

Yes, you can automate git commits across multi-repo worktrees. This workflow supports multi-repo development scenarios by staging all changes, including untracked files, and enforcing a consistent conventional commit history across multiple project worktrees.

What is a conventional commit and how does it enforce a clean git history?

A conventional commit is a standardized message format used to enforce a clean, reproducible git history. By requiring a conventional-commit style guide, the automation ensures all staged changes, including untracked files, follow consistent historical tracking across projects.

Does automated git commit staging work with untracked files in version control?

Automated git commit staging works directly with untracked files in version control. It stages all changes, including untracked files, ensuring that no new modifications are missed when creating a conventional commit in your repository.

Do I need a specific Git setup to automatically stage and commit all changes?

You need a Git repository, proper user configuration, and a conventional-commit style guide to automatically stage and commit all changes. These prerequisites ensure the automation can apply the policy automatically and support multi-repo worktree workflows effectively.