skills.rest
this-is-tobi
this-is-tobiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit-message

Generate conventional commit messages with type, scope, subject, body, and footers.

5|2|Updated Apr 2, 2023
Search Tags:#automation#git#devops#commit#conventional-commits#message
One-click install
npx skills add https://github.com/this-is-tobi/tools --skill commit-message-this-is-tobi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/this-is-tobi/tools/tree/main/copilot/skills/commit-message
Command: npx skills add https://github.com/this-is-tobi/tools --skill commit-message-this-is-tobi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often struggle to write consistent, properly formatted commit messages, leading to noisy history and broken automation that relies on Conventional Commits.

Core Features & Use Cases

  • Guided Type Selection: Chooses the appropriate commit type based on a quick question flow.
  • Structured Formatting: Enforces the Conventional Commits layout with optional scope, body, and footers.
  • Best‑Practice Enforcement: Ensures lowercase imperative subjects, length limits, and correct footer syntax.
  • Use Case: When a teammate asks for a commit message for a new feature or bug fix, this skill generates a ready‑to‑use message that fits CI/CD changelog generators.

Quick Start

Generate a conventional commit message for adding a new authentication endpoint.

Frequently Asked Questions about commit-message

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

FAQPage Schema
How do I generate conventional commit messages for my Git repository?▼

Conventional commit messages follow a specification enforcing lowercase imperative subjects, length limits, and correct footer syntax. This structured layout includes a type, optional scope, subject, and body, ensuring clean history and preventing broken automation that relies on consistent commit formatting.

What is the best way to format Git commits for CI/CD changelog automation?▼

The best way to format Git commits for CI/CD changelog automation is using Conventional Commits, which enforces a structured layout with type, optional scope, subject, and footers. This consistency allows automated changelog generators to parse repository history accurately.

Can I include a scope and body when creating a conventional commit message?▼

Yes, you can include an optional scope and body when creating a conventional commit message. The format enforces the Conventional Commits layout, allowing you to specify the type, scope, subject, body, and correct footer syntax according to the specification.

Why does my conventional commit message break changelog generation in DevOps pipelines?▼

Your conventional commit message likely breaks changelog generation due to formatting issues like missing types, non-imperative subjects, or incorrect footer syntax. Enforcing best practices with proper length limits and structured layout ensures CI/CD automation can parse commits correctly.

Related Skills

Explore More Software Engineering Skills→
mgoodman60mgoodman60

commit

Generate descriptive Git commit messages from repository changes with conventional formatting.

Community
Basic
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced
dorriodorrio

ln-742-precommit-setup

Configure Husky, lint-staged, commitlint, and Python pre-commit hooks.

Community
Intermediate
asd335w3dasd335w3d

git-commit-helper

Analyze Git diffs to generate Conventional Commits messages.

Community
Intermediate