commit

Generate Git commit messages following Sentry conventional commit standards.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/aldy505/atrium --skill commit-aldy505
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/aldy505/atrium/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/aldy505/atrium --skill commit-aldy505

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create clear, consistent, and informative Git commit messages that adhere to established conventions, improving code history readability and maintainability.

Core Features & Use Cases

  • Conventional Commits: Enforces a structured format for commit messages (<type>(<scope>): <subject>).
  • Sentry Conventions: Integrates Sentry-specific issue referencing and AI co-author attribution.
  • Use Case: When you've finished a bug fix, use this Skill to generate a commit message like fix(api): Resolve null pointer in user endpoint that clearly states the change and references the relevant issue.

Quick Start

Use the commit skill to generate a commit message for a new feature that adds user authentication.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages for Git?

To generate conventional commit messages for Git, this Skill applies Sentry's structured format, ensuring your commits include the correct type, scope, subject, body, and footer for better code history readability.

What is the Sentry conventional commit format for code refactoring?

The Sentry conventional commit format for code refactoring structures messages as `<type>(<scope>): <subject>`, integrating Sentry-specific issue referencing and AI co-author attribution within the commit body and footer.

How do I include issue tracking references in a Git commit message?

To include issue tracking references in a Git commit message, this Skill enforces Sentry conventions that place issue tracking references and AI co-authorship details directly into the structured commit footer.

Do I need any specific dependencies to use conventional commits?

You do not need any specific dependencies to use this conventional commits Skill, as it operates independently without requiring external modules to generate structured Git commit messages.

Can I use this for documentation updates or only for code commits?

You can use this for documentation updates as well as code commits and refactoring, because the Skill applies conventional commit standards across any changes made within a Git repository.