commit

Creates conventional commits with component scopes and Assisted-by trailers for Ansible collection changes.

8|7|Updated Feb 14, 2023
One-click install
npx skills add https://github.com/eclipse-slm/slm --skill commit-eclipse-slm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/eclipse-slm/slm/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/eclipse-slm/slm --skill commit-eclipse-slm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, standards-compliant git commit messages is error-prone and time-consuming, especially when following the Conventional Commits specification with project-specific conventions like component scopes and AI attribution trailers. ## Core Features & Use Cases - Conventional Commit Generation: Infers the correct commit type (feat, fix, docs, chore, refactor, ci, deprecate, remove, breaking) from changelog fragments or the nature of the changes. - Message Formatting Rules: Enforces subject lines under 72 characters, imperative mood, lowercase descriptions, and BREAKING CHANGE footers. - AI Attribution: Automatically appends an Assisted-by trailer identifying the AI model and version used in the session. - Use Case: After modifying an Ansible role or module, ask the assistant to commit the changes and receive a properly formatted message like "feat: add support for custom agent port to postgresql_info module" with user confirmation before committing. ## Quick Start Ask the assistant to commit your staged changes with a conventional commit message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create a conventional commit message with git?▼

Use the format type(scope): description, such as feat(auth): add login endpoint. Keep the subject under 72 characters, use imperative mood, lowercase after the colon, and add a BREAKING CHANGE footer for incompatible changes.

How to write commit messages for Ansible collection changes?▼

Use conventional commits with the component as scope, like feat(postgresql_info): add custom agent port support. Infer the type from changelog fragments when present, or from whether the change adds features, fixes bugs, or updates documentation.

What commit types does Conventional Commits support?▼

This workflow supports feat, fix, docs, chore, refactor, ci, deprecate, remove, and breaking types. Breaking changes can also be marked with an exclamation mark after the type, like feat!, plus a BREAKING CHANGE footer explaining the impact.

Does the commit skill require user confirmation before committing?▼

Yes, the skill always presents the proposed commit message for approval before running git commit. If you provide an edited message, it uses your version exactly instead of the generated draft.

Why add an Assisted-by trailer to git commits?▼

The Assisted-by trailer records which AI model and version helped create the commit, providing transparency about AI-assisted contributions. It is appended after a blank line at the end of every commit message, such as Assisted-by: Claude Sonnet 4.6.