git-commit-for-ai-agents
Commit changes to a git repository. Use whenever a git commit is to be executed.
Best use case
git-commit-for-ai-agents is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Commit changes to a git repository. Use whenever a git commit is to be executed.
Teams using git-commit-for-ai-agents should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/git-commit-for-ai-agents/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How git-commit-for-ai-agents Compares
| Feature / Agent | git-commit-for-ai-agents | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Commit changes to a git repository. Use whenever a git commit is to be executed.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
**CRITICAL**: A commit to git must **always** be the result of explicit requests, and **never** can be done automatically. ### Files - **Always** follow the rules found in `.gitignore` files. - If agent is Claude, ensure that the setting `respectGitignore` is set to `true`. ### Commit message - **Always** limit line text to 72 characters. - **CRITICAL**: Always add "Assisted-by: AGENT IDENTIFICATION <AGENT E-MAIL>" - **CRITICAL**: Always commit with '-s/--signoff' - Each commit should represent a single, logical change - Use bullet points for multiple changes. - **CRITICAL**: Always add a bullet list of the prompts used to generate the change being commited. - **NEVER** add promps like "commit changes" to the list of prompts. - The message summary should contain the component that is affected by the changes and then a brief summary of the changes. This is an example of a good commit message: ``` CLAUDE.md: Sync with AGENTS.md and add sync rule Updated CLAUDE.md to include all rules from AGENTS.md: - Added AGENTS.md synchronization check requirement - Added rule to ignore docs/prompts.md when analyzing - Expanded commit message rules to include prompt tracking - Added requirement for single logical change per commit - Added .gitignore compliance requirement - Reorganized Git section into Files and Commit Message subsections Prompts: - Update CLAUDE.md with current AGENTS.md, and add a rule to always update it again, if AGENTS.md is newer than CLAUDE.md Assisted-by: Claude Sonnet 4.5 <noreply@anthropic.com> Signed-off-by: Rafael Guterres Jeffman <rjeffman@redhat.com> ```
Related Skills
langchain-agents
Expert guidance for building LangChain agents with proper tool binding, memory, and configuration. Use when creating agents, configuring models, or setting up tool integrations in LangConfig.
kramme:agents-md
This skill should be used when the user asks to "update AGENTS.md", "add to AGENTS.md", "maintain agent docs", or needs to add guidelines to agent instructions. Guides discovery of local skills and enforces structured, keyword-based documentation style.
dispatching-parallel-agents
Use when facing 3+ independent failures that can be investigated without shared state or dependencies. Dispatches multiple Claude agents to investigate and fix independent problems concurrently.
custom-sub-agents
Guidance for creating and organizing custom sub-agents in local repos, including folder conventions, per-agent structure, and AGENTS.md indexing. Use when asked where to store sub-agents or how to document them.
custom-agents
GitHub Custom Agent File Format
creating-agents
Create and review agent definition files (agents.md) that give AI coding agents a clear persona, project knowledge, executable commands, code style examples, and explicit boundaries. Use when a user asks to create an agent, define an agent persona, write an agents.md file, set up a custom Copilot agent, review an existing agent definition, or improve agent quality. Covers the six core areas: commands, testing, project structure, code style, git workflow, and boundaries.
create-agents-md
Create or rewrite AGENTS.md files for Open Mercato packages and modules. Use this skill when adding a new package, creating a new module, or when an existing AGENTS.md needs to be created or refactored. Ensures prescriptive tone, MUST rules, checklists, and consistent structure across all agent guidelines.
building-agents
Expert at creating and modifying Claude Code agents (subagents). Auto-invokes when the user wants to create, update, modify, enhance, validate, or standardize agents, or when modifying agent YAML frontmatter fields (especially 'model', 'tools', 'description'), needs help designing agent architecture, or wants to understand agent capabilities. Also auto-invokes proactively when Claude is about to write agent files (*/agents/*.md), create modular agent architectures, or implement tasks that involve creating agent components.
audit-agents-md
Audit AGENTS.md files for token efficiency, completeness, scope hygiene, and actionability. Also considers skills and Cursor rules for redundancy. Use when the user wants to review, optimize, or restructure project agent instructions.
ai-coding-agents
Comprehensive guide for using Codex CLI (OpenAI) and Claude Code CLI (Anthropic) - AI-powered coding agents. Use when orchestrating CLI commands, automating tasks, configuring agents, or troubleshooting issues.
ai-agents
Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, observability, token economics, ROI frameworks, and build-vs-not decision guidance (modern best practices)
agents-v2-py
Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry.