af-git-commit

Analyze staged changes and plan context to generate structured git commit messages.

1|Updated Nov 12, 2025

Search Tags:#automation #git #planning #commit #version-control #ai-attribution

Ready to run

npx skills add https://github.com/e-stpierre/agentic-forge --skill af-git-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: af-git-commit
Source: https://github.com/e-stpierre/agentic-forge/tree/main/src/claude/.claude/skills/git-commit
Command: npx skills add https://github.com/e-stpierre/agentic-forge --skill af-git-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of well-structured git commits, saving time and reducing human error in change history.

Core Features & Use Cases

Structured commit messages with a clear title, optional description, and plan references like [Task N] or [Milestone N].
AI-attribution included in every commit to ensure traceability.
Plan-aware commits that extract the current task or milestone context and format the commit accordingly for reproducible workflows.
Use cases: small bug fixes, incremental features, and milestone-driven updates across collaborative teams.

Quick Start

Stage your changes and invoke the commit tool to generate a structured, plan-aware git commit with AI attribution.

Frequently Asked Questions about af-git-commit

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

FAQPage Schema

How do I automate structured git commit messages with plan references?▼

Automating structured git commits involves analyzing staged changes and active plan context to produce a formatted message with task prefixes like [Task N] and AI attribution for reproducible workflows.

What is AI attribution in version control and why include it in commits?▼

AI attribution in version control is metadata appended to commit messages ensuring traceability of AI-assisted changes within the collaborative change history.

How do I create a plan-aware git commit for milestone-driven updates?▼

Creating a plan-aware git commit requires extracting current task or milestone context from an active plan and formatting the commit message accordingly before executing a safe, heredoc-based commit.

Do I need to manually stage changes before generating an automated commit?▼

Yes, you must stage your changes manually before invoking automation, as the tool analyzes already staged changes and active plan context to produce the final commit message.

What is the safest way to format automated git commit messages?▼

Using a heredoc-based git commit command is the safest formatting method, preventing shell interpretation issues when passing multi-line titles, descriptive bodies, and plan prefixes.

Can I use automated commit messages for incremental features and bug fixes?▼

Yes, automated commit messages suit small bug fixes, incremental features, and milestone-driven updates, reducing human error and saving time across collaborative team workflows.