commit

Draft commit messages from staged code changes using the seven rules.

Updated Dec 13, 2019
One-click install
npx skills add https://github.com/polaroidkidd/dle.dev --skill commit-polaroidkidd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/polaroidkidd/dle.dev/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/polaroidkidd/dle.dev --skill commit-polaroidkidd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft readable, changelog-friendly commit messages from code changes to improve traceability and collaboration.

Core Features & Use Cases

  • Draft a subject line that follows the seven rules for great commit messages.
  • Compose a body that explains what changed and why, and maps the entry to relevant Keep a Changelog categories.
  • Review staged work to ensure a cohesive, single-issue commit before pushing.

Quick Start

Inspect your staged changes and draft a single, compliant commit message following the seven rules.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write a changelog-ready git commit message from code changes?

To write a changelog-ready git commit message, draft a subject line following the seven rules for great commit messages, then compose a body explaining what changed and why, mapping the entry to Keep a Changelog categories for clear traceability.

What are the seven rules for writing great git commit messages?

The seven rules for great git commit messages guide you to draft readable, cohesive entries that clearly state what changed and why. This approach ensures your commit is changelog-friendly and mapped to relevant Keep a Changelog categories before pushing.

How do I map code changes to Keep a Changelog categories in a commit?

To map code changes to Keep a Changelog categories, review your staged work and compose a commit body that explains what changed and why, categorizing the entry appropriately to generate a single, cohesive, changelog-friendly commit.

Can I review staged work to ensure a single cohesive git commit before pushing?

Yes, you can review staged work to ensure a single cohesive git commit before pushing. This process verifies your changes represent one issue, allowing you to draft a compliant commit message that clearly states what changed and why.

Does this commit drafting workflow work without extra dependencies?

Yes, this commit drafting workflow works without extra dependencies. You simply inspect your staged changes and draft a single, compliant commit message following the seven rules and mapping entries to relevant Keep a Changelog categories.