git-commit

Automate git staging, committing, and pushing with conventional messages.

Updated Jan 27, 2026

Search Tags:#git #workflow #commit #safety #staging #push #version-control

Ready to run

npx skills add https://github.com/alistairhendersoninfo/ninja_toolbox --skill git-commit-alistairhendersoninfo

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured workflow for staging, committing, and pushing changes in git to reduce mistakes and ensure a clean history.

Core Features & Use Cases

Guided workflow: Step-by-step guidance from git status to pushing changes.
Safety guardrails: Warns about sensitive files and prevents accidental commits.
Reusable templates: Encourages clear, conventional commit messages for teams.

Quick Start

Run a guided git commit workflow by checking status, staging intentional changes, and composing a clear commit message.

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I automate structured git commits to avoid staging sensitive files?▼

To automate structured git commits, use a guided workflow that runs git status and git diff, explicitly stages changes, and blocks sensitive files before composing a conventional commit message. This reduces mistakes and maintains a clean history.

What is the best way to enforce conventional commit messages in a collaborative repository?▼

Enforcing conventional commit messages in a collaborative repository requires a structured commit workflow that guides staging and pushing changes using reusable templates. This ensures clear history and safer version control across feature branches and bugfix patches.

Does this git workflow support feature branches and bugfix patches?▼

Yes, this structured git commit workflow applies across feature branches and bugfix patches. It guides staging, committing, and pushing changes to ensure safer version control and clean history in collaborative repositories.

How do I review git diffs before staging changes for a commit?▼

Reviewing git diffs before staging changes for a commit requires a multi-step workflow that runs git status and git diff to inspect modifications. Explicit staging then ensures only intentional changes are committed while sensitive files are guarded.

Why should I use explicit staging instead of git commit -a for version control?▼

Using explicit staging instead of git commit -a is safer for version control because it enforces a multi-step process that reviews git status and git diff first. This guards against committing sensitive files and ensures only intentional changes are staged.

When should I not use an automated git commit workflow?▼

You should not use an automated git commit workflow when dealing with unstaged sensitive files that require manual review, or when bypassing the structured multi-step process of checking git status and git diff before pushing changes to collaborative repositories.