git-commit

Automate git commits via a Bash subagent with conventional messages.

Updated Sep 9, 2017

Search Tags:#automation #git #workflow #commit #bash #devtools #version-control

Ready to run

npx skills add https://github.com/mirakui/dotfiles --skill git-commit-mirakui

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/mirakui/dotfiles/tree/main/claude/skills/git-commit
Command: npx skills add https://github.com/mirakui/dotfiles --skill git-commit-mirakui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates git commit workflows by delegating all repository changes to a Bash subagent. This keeps the main context clean and ensures a clear, final summary of the changes is returned.

Core Features & Use Cases

Delegates git operations to a Bash subagent to keep the main context focused on outcomes.
Performs status checks, inspects diffs, and stages files selectively while skipping sensitive items.
Generates conventional commit messages and provides a concise summary for review.
Useful for daily coding, documentation updates, and small configuration changes that require safe, traceable commits.

Quick Start

Ask the skill to review changes, stage files safely, and create a conventional commit.

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I automate git commits with conventional commit messages?▼

Automate git commits by delegating repository status checks, diff reviews, and selective staging to a Bash subagent. The workflow generates conventional commit messages for code changes while keeping the main context clean and returning a final summary.

Can I selectively stage files for a git commit while skipping sensitive items?▼

Yes, you can selectively stage files for a git commit while skipping sensitive items. The workflow inspects repository status and diffs first, ensuring only safe, intended code changes and configuration updates are staged before generating the commit message.

Does automated git commit workflow handle pre-commit hook errors?▼

Automated git commit workflows include error handling for pre-commit hooks. If a hook fails during the commit process, the Bash subagent catches the error to prevent broken commits and maintain safe version-control practices.

What's the best way to safely push git commits after generating conventional messages?▼

The best way to push git commits safely is using an optional push confirmation step. After generating a conventional commit message and staging files, the workflow prompts for confirmation before pushing changes to the remote repository.

Do I need a Bash subagent to automate git status inspection and diff review?▼

Yes, a Bash subagent is required to automate git status inspection and diff review. Delegating all repository changes to Bash ensures that git operations execute correctly while keeping the main assistant context focused on outcomes.

Why use a subagent for git commit automation instead of running commands directly?▼

Using a subagent for git commit automation keeps the main context clean by isolating verbose git command outputs. It ensures a clear, final summary of staged changes and conventional commit messages is returned without cluttering the conversation.