kramme:commit

Name: kramme:commit
Availability: InStock
Author: abildtoft

Generate descriptive commit messages with subject and body guidelines.

2|2|Updated Jan 15, 2026

Search Tags:#git #commit #code-quality #software-engineering #pull-request #change-management

Ready to run

npx skills add https://github.com/Abildtoft/kramme-cc-workflow --skill kramme-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kramme:commit
Source: https://github.com/Abildtoft/kramme-cc-workflow/tree/main/skills/kramme%3Acommit
Command: npx skills add https://github.com/Abildtoft/kramme-cc-workflow --skill kramme-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of clear, descriptive commit messages for code changes.

Core Features & Use Cases

Guided Commit Messages: Enforces concise subject lines and informative bodies aligned with project conventions.
Issue & PR References: Automatically includes issue numbers and PR references when provided.
Use Case: When preparing a feature or bugfix for review, generate a message that clearly communicates the change and intent.

Quick Start

Provide a concise description of the change, and ask the AI to generate a commit message, e.g., "Add login endpoint with JWT support".

Frequently Asked Questions about kramme:commit

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

FAQPage Schema

How do I generate clear git commit messages for code changes?▼

To generate clear git commit messages, provide a concise description of your code changes. The skill enforces subject and body guidelines, includes issue references, and avoids AI attribution markers for descriptive results.

What is the best way to format commit messages for a pull request?▼

The best way to format pull request commit messages is by enforcing concise subject lines and informative bodies. This approach aligns with project conventions and automatically includes issue numbers when provided.

How do I write a descriptive commit message for a bug fix or feature?▼

Writing a descriptive commit message for a bug fix or feature requires providing the change description. The skill then generates a message that clearly communicates the change and intent during development.

Can I include issue references and PR numbers in my git commit messages?▼

Yes, you can include issue references and PR numbers in git commit messages. When provided, they are automatically integrated into the structured commit message alongside the descriptive subject and body.

Does the generated commit message include AI attribution markers?▼

Generated commit messages do not include AI attribution markers. The skill specifically avoids these markers to ensure your software engineering commit history remains clean and consistent.

What do I need to provide to automate commit message creation?▼

To automate commit message creation, you need to provide a concise description of your code change, such as "Add login endpoint with JWT support". The system then generates a structured message aligned with project conventions.