Skip to content
Back to skills

Git Commit For Ai Agents

ASecurity

Commit changes to a git repository. Use whenever a git commit is to be executed.

  • 57 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 17, 2026
ai-agentsgogit

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add diegosouzapw/awesome-omni-skill --skill git-commit-for-ai-agents --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Git Commit For Ai Agents?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Git Commit For Ai Agents
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/diegosouzapw-git-commit-for-ai-agents/badge)](https://www.skillsdirectory.com/skills/diegosouzapw-git-commit-for-ai-agents)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: git-commit-for-ai-agents
description: Commit changes to a git repository. Use whenever a git commit is to be executed.
license: GPL-3.0-or-later
compatibility: Requires git.
metadata:
  author: Rafael Guterres Jeffman <rjeffman@redhat.com>
  version: "1.0"
---

**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>
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.