commit-author

Generate Conventional Commit messages from staged Git diffs.

3|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/ralvarezdev/ralvaskills --skill commit-author
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-author
Source: https://github.com/ralvarezdev/ralvaskills/tree/main/skills/workflows/commit-author
Command: npx skills add https://github.com/ralvarezdev/ralvaskills --skill commit-author

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate concise Conventional Commits messages from a staged diff, enforcing a full type set, imperative subjects, and prohibition of AI co-authorship to ensure consistent, auditable commit histories.

Core Features & Use Cases

  • Generate a Conventional Commit from the current staged diff following the Angular-style type set.
  • Enforce imperative subject lines, 50-character limit, and proper body/footer formatting.
  • Use in code reviews, feature work, bug fixes, and maintenance tasks to maintain clean Git history.

Quick Start

Provide the staged changes and ask me to create a Conventional Commit message.

Frequently Asked Questions about commit-author

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

FAQPage Schema
How do I generate Conventional Commits from a staged diff?▼

To generate Conventional Commits from a staged diff, provide the staged changes to the tool to produce a standardized commit message. It enforces the Angular-style type set, imperative subject lines, and proper body formatting to ensure a clean Git history.

What is the best way to enforce a 50-character limit and imperative mood in git commit messages?▼

The best way to enforce a 50-character limit and imperative mood in git commit messages is to use an automated generator that parses staged diffs. It formats the subject line according to Angular-style coding standards, ensuring consistent, auditable histories.

Does this commit message generator support feature development, bug fixes, and maintenance tasks?▼

Yes, this commit message generator supports feature development, bug fixes, and maintenance tasks across Git workflows. It applies the full Angular-style type set to categorize each staged diff accurately for consistent version control history.

Why are AI co-authorship lines disallowed in conventional commit histories?▼

AI co-authorship lines are disallowed to ensure consistent, auditable commit histories without automated attribution noise. This maintains strict coding standards and keeps the Git log focused on human-authored changes and conventional commit formatting.

Can I use this tool to standardize commit history without manually writing the subject line?▼

Yes, you can standardize commit history without manually writing the subject line by passing the staged diff to the generator. It automatically outputs a concise conventional commit with an enforced imperative subject and proper body formatting.

What are the limitations of using automated conventional commit generation for coding standards?▼

A limitation of automated conventional commit generation is that it relies strictly on the provided staged diff context. It enforces the Angular-style type set and disallows AI co-authorship, meaning it cannot infer changes outside the current staged files.