hello-commit

Generates git commit messages with a custom prefix after reviewing staged changes.

1.1k|96|Updated Feb 6, 2026

Search Tags:#Git #extension #Workflow #AI-factory #Commit #skill replacement

Ready to run

npx skills add https://github.com/lee-to/ai-factory --skill hello-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hello-commit
Source: https://github.com/lee-to/ai-factory/tree/main/examples/extensions/aif-ext-hello/skills/hello-commit
Command: npx skills add https://github.com/lee-to/ai-factory --skill hello-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It demonstrates how to override the built-in aif-commit workflow in AI Factory by providing a custom commit process that inspects staged changes and creates prefixed commit messages.

Core Features & Use Cases

Skill Replacement: Replaces the built-in aif-commit skill to showcase the extension system's replaces feature.
Guided Commit Workflow: Runs git status and git diff --cached, suggests staging when nothing is staged, and asks for confirmation before committing.
Prefixed Messages: Generates commit messages with a [hello] prefix for easy identification.
Use Case: A developer building an AI Factory extension can use this skill as a reference implementation for overriding default behaviors with custom workflows.

Quick Start

Ask the agent to commit your staged changes using the custom hello-commit workflow and confirm the generated prefixed message.

Frequently Asked Questions about hello-commit

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

FAQPage Schema

How do I replace a built-in AI Factory skill with a custom one?▼

Create a skill in your extension's skills directory that declares the replacement via the replaces feature, as demonstrated by hello-commit overriding aif-commit. The extension system then routes invocations to your custom skill instead of the default.

How does the custom commit workflow generate commit messages?▼

It runs git status and git diff --cached to inspect staged changes, generates a message with a [hello] prefix, asks for your confirmation, and then executes git commit. If nothing is staged, it suggests staging first.

Can I use this skill without staging changes first?▼

No, the workflow checks git status and git diff --cached first. If nothing is staged, it suggests staging your changes before proceeding with commit message generation.

What git permissions does this skill require?▼

The skill declares allowed-tools as Bash(git *), meaning it can only run git commands. It cannot execute arbitrary shell commands outside the git CLI.