commit-generator

Generate conventional commit messages from approved task IDs and titles.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/alexanderjamesmcleod/makecents --skill commit-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-generator
Source: https://github.com/alexanderjamesmcleod/makecents/tree/main/src/skills/business/commit-generator.skill
Command: npx skills add https://github.com/alexanderjamesmcleod/makecents --skill commit-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated generation of conventional commit messages from approved tasks eliminates the manual drafting effort, reduces human error, and accelerates release workflows.

Core Features & Use Cases

  • Auto-discovery of approved tasks and extraction of TASK IDs and titles
  • Automatic detection of commit type and scope to produce conventional commits
  • Generation of a copy-ready commit message and optional git command
  • Support for single or multi-task scenarios with clear summarization

Quick Start

Describe the approved tasks and ask the skill to generate a conventional commit message.

Frequently Asked Questions about commit-generator

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

FAQPage Schema
How do I automatically generate conventional commit messages from tasks?

To generate conventional commit messages from tasks, describe your approved tasks and the system scans them, parses IDs and titles, and auto-detects the type and scope to produce a standards-compliant message.

What is the best way to format multiple task descriptions into a single git commit?

Formatting multiple task descriptions into a single git commit is handled by supporting multi-task scenarios, computing git statistics, and generating a clear, copy-ready summarization with an optional git command.

Can I use conventional commits automation without manually specifying the commit type and scope?

Yes, conventional commits automation can be used without manual input by auto-detecting the commit type and scope directly from the parsed task IDs and titles of your approved tasks.

Does this commit message generator work for both single and multi-task scenarios?

This commit message generator works for both single and multi-task scenarios, gracefully extracting task IDs and titles to produce standards-compliant output with clear summarization.

Why do I need conventional commits for my git workflow automation?

You need conventional commits for git workflow automation to eliminate manual drafting effort, reduce human error, and accelerate release workflows with standards-compliant messages.

What should I provide to start automating conventional commit messages?

To start automating conventional commit messages, you should describe the approved tasks so the system can parse the IDs and titles, auto-detect type and scope, and generate a copy-ready message.