skills.rest
Paxeer-Network
Paxeer-NetworkOFFICIAL
Explore all skills by this author →
Website𝕏@paxeer_appGitHub

examples

Provide Conventional Commits examples across commit types and scopes.

3|2|Updated Feb 11, 2026
Search Tags:#git#documentation#version control#developer workflow#conventional commits#commits
One-click install
npx skills add https://github.com/Paxeer-Network/Sidiora-Perpetual-Protocol --skill examples-paxeer-network
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: examples
Source: https://github.com/Paxeer-Network/Sidiora-Perpetual-Protocol/tree/main/.windsurf/skills/writing-git-commits/examples
Command: npx skills add https://github.com/Paxeer-Network/Sidiora-Perpetual-Protocol --skill examples-paxeer-network

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides clear, real-world examples of Conventional Commits, helping developers write better, more standardized commit messages for improved project clarity and automated changelog generation.

Core Features & Use Cases

  • Illustrates Commit Types: Demonstrates feat, fix, docs, refactor, test, chore, ci, style, perf.
  • Shows Scope and Body Usage: Explains how to add context and detail to commits.
  • Highlights Breaking Changes: Provides examples of ! notation and BREAKING CHANGE footers.
  • Use Case: A developer unsure how to format a commit for a new feature with a breaking change can refer to this Skill for a correct example, ensuring consistency across the team.

Quick Start

Show me an example of a Conventional Commit for a bug fix with a detailed body.

Frequently Asked Questions about examples

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

FAQPage Schema
What is a Conventional Commit and when should I use it?▼

A Conventional Commit is a standardized commit message format used to improve project clarity and automate changelog generation. You should use it to enforce imperative mood and specific descriptions across software development scenarios.

How do I write a Conventional Commit for a bug fix with a detailed body?▼

To write a Conventional Commit for a bug fix, use the `fix` type followed by an optional scope and a specific description. Add a detailed body after the header to provide context and explain the changes.

How do I indicate breaking changes in Conventional Commits?▼

Indicate breaking changes in Conventional Commits by adding a `!` after the commit type or scope, or by including a `BREAKING CHANGE` footer. This notation highlights changes that require action.

What commit types are available in the Conventional Commits specification?▼

Available commit types include `feat`, `fix`, `docs`, `refactor`, `test`, `chore`, `ci`, `style`, and `perf`. Each type categorizes the developer workflow action for automated processing.

Does Conventional Commits work with my existing version control workflow?▼

Yes, Conventional Commits integrates with existing Git workflows by standardizing commit message formatting. It enforces specific descriptions and optional scope usage without altering your underlying version control operations.

When should I not use an optional scope in a Conventional Commit?▼

Avoid using an optional scope when the commit applies globally rather than to a specific module. Omit the scope to prevent misclassification and keep the commit message focused on the overall change.

Related Skills

Explore More Software Engineering Skills→
Tx1207Tx1207
5

project-creator

Create a new project from a template, initialize uv, and configure a local Git repository.

Community
Advanced
OnClickListener2048OnClickListener2048

chinese-commit-conventions

Enforce Chinese commit conventions and generate changelogs from Git history.

Community
Intermediate
avvaleavvale

conventional-commits

Validate commit messages against the Conventional Commits specification.

Official
Basic
coff33ninjacoff33ninja

git-workflow-conventional-commits

Enforce conventional commit format and atomic commit conventions in git workflows.

Community
Advanced