git-commit

Generate Git commit messages following Conventional Commits and Sentry conventions.

7|2|Updated Jan 28, 2026

Search Tags:#git #version control #commit #conventional commits #code history #sentry

Ready to run

npx skills add https://github.com/LuisSambrano/antigravity-config --skill git-commit-luissambrano

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/LuisSambrano/antigravity-config/tree/main/skills/1-core/git-commit
Command: npx skills add https://github.com/LuisSambrano/antigravity-config --skill git-commit-luissambrano

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures your Git commit messages are consistent, informative, and follow established conventions, improving code history clarity and collaboration.

Core Features & Use Cases

Conventional Commits: Adheres to the conventional commit specification for structured commit messages.
Sentry Issue Referencing: Integrates Sentry-specific issue tracking into commit footers.
AI Co-Authorship: Standardizes attribution for AI-generated code contributions.
Use Case: When you've completed a bug fix, use this skill to generate a commit message like fix(api): Resolve null pointer in user endpoint. Fixes SENTRY-1234. Co-Authored-By: Claude <[email protected]>.

Quick Start

Use the git-commit skill to create a commit message for a new feature that adds user authentication.

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I generate Git commit messages that follow conventional commits?▼

Conventional commit messages are generated by enforcing structured type, scope, subject, body, and footer guidelines. This standardizes code history clarity and improves collaboration by making commit intent immediately recognizable.

Can I reference Sentry issues in my conventional commit footers?▼

Yes, you can reference Sentry issues in conventional commit footers. This integrates Sentry-specific issue tracking into your commit history, directly linking code changes to tracked bugs and resolutions like 'Fixes SENTRY-1234'.

What is the best way to attribute AI-generated code in Git history?▼

The best way to attribute AI-generated code in Git history is using the Co-Authored-By trailer in the commit footer. This standardizes attribution for contributions from LLMs, such as 'Co-Authored-By: Claude <[email protected]>'.

Does this Git commit message generator work without additional dependencies?▼

Yes, this Git commit message generator works without additional dependencies. It operates as a standalone reference component to craft structured commit messages, requiring no external packages or complex environment setup.

How do I structure a bug fix commit message with Sentry and GitHub references?▼

To structure a bug fix commit message with Sentry and GitHub references, use the 'fix' type followed by the scope. Add a clear subject, then use the footer to link issues, like 'fix(api): Resolve null pointer. Fixes SENTRY-1234.'.