commit

Generate single-line conventional commit messages under 72 characters.

17.5k|1.1k|Updated May 5, 2022
One-click install
npx skills add https://github.com/windmill-labs/windmill --skill commit-windmill-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/windmill-labs/windmill/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/windmill-labs/windmill --skill commit-windmill-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams eliminate inconsistent or vague commit messages by enforcing the conventional commit format across changes.

Core Features & Use Cases

  • Enforces conventional commit types (feat, fix, refactor, docs, style, test, chore, perf)
  • Guides staging of only modified files, preventing accidental bulk commits
  • Generates a single-line, compliant commit message suitable for automated changelog generation and reviews
  • Use Case: when preparing a release or sharing changes across a CI pipeline with a consistent history

Quick Start

Generate a single-line conventional commit message for the current changes

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write conventional commit messages for git?

Conventional commits follow a format like `type(scope): description` to standardize messages across teams. This Skill generates single-line conventional commit messages (feat, fix, refactor, docs, style, test, chore, perf) under 72 characters, ensuring consistency for automated changelog generation and code reviews.

What's the best way to automate consistent git commit messages?

Enforce a conventional commit format across your team to eliminate vague messages and enable automated tooling. This Skill generates compliant single-line messages and guides staging of only modified files, preventing accidental bulk commits.

How do I stage only modified files before committing?

Staging only changed files prevents unintended additions to your commit. This Skill guides you to stage modified files selectively, then generates a conventional commit message for those staged changes.

Can I use conventional commits with CI/CD pipelines?

Yes. Conventional commits enable automated changelog generation and version control integration. This Skill produces compliant single-line messages suitable for CI pipelines that parse commit history and trigger release workflows.

Why enforce a single-line commit message under 72 characters?

Single-line messages under 72 characters improve readability in logs and emails, and comply with conventional commit standards. This format ensures messages display properly in git tools and automated processes that parse commit history.

Does this work with development workflows that use feature branches?

Yes. Conventional commits apply to any git workflow, including feature branches. This Skill generates consistent commit messages for changes on branches before merging, improving traceability across your development workflow.