git_commit

Stage the full working tree and generate an evidence-based git commit message.

38|7|Updated May 3, 2026
One-click install
npx skills add https://github.com/theafh/ai-modules --skill git-commit-theafh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git_commit
Source: https://github.com/theafh/ai-modules/tree/main/plugins/ai_dev/skills/git_commit
Command: npx skills add https://github.com/theafh/ai-modules --skill git-commit-theafh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill removes the friction of manually staging and composing a coherent single commit message that accurately reflects the full current working-tree state.

Core Features & Use Cases

  • Structured evidence capture: Collects status, recent commits, and per-file staged and unstaged diffs (including binary-change markers) into a single context blob.
  • One-shot commit execution: Stages the full repo state and creates exactly one commit using a commit message composed from the captured evidence.
  • Safety guardrails & fallback: If the primary scripted workflow fails, it proceeds via an authorized manual fallback procedure to reproduce the same evidence and complete the commit.

Quick Start

Ask the AI to make a git commit for the current repo state, and then provide the commit message guidance if you want to override the default messaging policy.

Frequently Asked Questions about git_commit

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

FAQPage Schema
How do I create a single git commit for multiple unstaged and staged files?

To create a single git commit across multiple files, this Skill captures all per-file diffs and recent commit history, then stages the full working-tree state and generates one structured commit message based on that captured evidence.

How do I generate an accurate git commit message from my repository diff?

Generating an accurate git commit message requires capturing authoritative per-file diffs and repository status first. This Skill reads the entire diff context to compose a low-hallucination message that accurately reflects the working-tree changes for code review.

What is the best way to automate a developer workflow commit across multiple files?

The best way to automate a developer workflow commit is to run a scripted context capture of your repository status and diffs, then execute a single commit command that stages the complete repo state and applies an evidence-based commit message.

Can I use this git commit process if my primary staging script fails?

Yes, you can use this git commit process if the primary scripted workflow fails, because it includes an authorized manual fallback procedure that reproduces the same repository diff evidence and completes the commit execution.

Does this git commit tool support binary file changes in the diff context?

Yes, this git commit tool supports binary file changes by including binary-change markers in the structured context blob alongside staged and unstaged diffs, ensuring the commit message reflects all modifications accurately.

Do I need to manually run git diff before staging the complete repository?

No, you do not need to manually run git diff before staging the complete repository, because the Skill executes a prepare script that automatically captures the authoritative per-file diffs, recent commits, and working-tree status for you.