swpm-conventional-commits

Enforce Conventional Commits 1.0.0 formatting for SWPM projects.

125|5|Updated May 13, 2022

Search Tags:#git #semver #scope #conventional-commits #type #commit-messages #swpm

Ready to run

npx skills add https://github.com/deinsoftware/swpm --skill swpm-conventional-commits

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: swpm-conventional-commits
Source: https://github.com/deinsoftware/swpm/tree/main/.agents/skills/swpm-conventional-commits
Command: npx skills add https://github.com/deinsoftware/swpm --skill swpm-conventional-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional Commits 1.0.0 standard for SWPM defines the commit message structure with types (feat, fix, etc.), scopes, breaking changes, and body/footer conventions to ensure consistent history and clear release notes.

Core Features & Use Cases

Enforces commit message structure with mandatory type and optional scope.
Validates presence of body and footer sections for breaking changes and references.
Improves release planning and changelog generation by standardizing messages across SWPM projects.

Quick Start

Provide your next commit using a valid type, an optional scope, and proper body and footer sections according to the standard.

Frequently Asked Questions about swpm-conventional-commits

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

FAQPage Schema

How do I format git commit messages for SWPM projects?▼

Git commit message formatting for SWPM uses Conventional Commits 1.0.0 standards. You must include a mandatory type, an optional scope, and proper body and footer sections to ensure consistent history and clear release notes.

What is the conventional commits structure needed for automated changelog generation?▼

Automated changelog generation requires a conventional commits structure with a mandatory type like feat or fix, an optional scope, and body or footer sections for breaking changes and references to standardize release planning.

How do I indicate breaking changes in a conventional commit message?▼

To indicate breaking changes in a conventional commit message, use specific body and footer conventions. The standard requires these sections to document breaking changes and references for SWPM workflows and release processes.

Can I use conventional commits with custom scopes in CI pipelines?▼

You can use conventional commits with custom scopes in CI pipelines. The standard applies when writing or modifying commits across SWPM workflows and CI pipelines, supporting mandatory types with optional scopes for validation.

Why do I need a commit type and scope for SWPM release processes?▼

A commit type and scope are needed for SWPM release processes to enforce consistent message structure. This standardization improves release planning and changelog generation by identifying features, fixes, and breaking changes across projects.