# Git Conventional Commits

> Guide the user and agent to use conventional commits format for git messages. Use this skill when the user asks to "commit changes", "create a release", "explain commit format", or when performing any git commit action.

- **Type:** Skill
- **Install:** `agentstack add skill-michaeld-42-agentic-skills-git-conventional-commits`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [MichaelD-42](https://agentstack.voostack.com/s/michaeld-42)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [MichaelD-42](https://github.com/MichaelD-42)
- **Source:** https://github.com/MichaelD-42/agentic-skills/tree/main/skills/git-conventional-commits

## Install

```sh
agentstack add skill-michaeld-42-agentic-skills-git-conventional-commits
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Conventional Commits & Semantic Release

## Overview

This skill ensures that all git commit messages follow the [Conventional Commits](https://www.conventionalcommits.org/) specification. This structure enables automated versioning (Semantic Release) and creates a standardized project history.

## Core Format

```
(): 

[optional body]

[optional footer(s)]
```

### Key Rules

1.  **Type:** Must be one of the allowed types (see `references/commit-types.md`).
2.  **Scope:** Optional but recommended. Describes the part of the codebase affected (e.g., `physics`, `ui`, `deps`).
3.  **Description:** concise summary in imperative mood ("add" not "added").
4.  **Breaking Changes:** Must be indicated by a `!` after the type/scope or a `BREAKING CHANGE:` footer.

## When to Use This Skill

- Before running `git commit`.
- When the user asks to "save changes".
- When explaining why a version number bumped (Semantic Versioning).

## Reference Index

### 1. Allowed Types

> **See: `references/commit-types.md`**
>
> detailed list of types (`feat`, `fix`, `chore`, etc.) and their impact on version numbers.

### 2. Examples

> **See: `references/examples.md`**
>
> Good and bad examples of commit messages, including breaking changes.

## Workflow

1.  **Identify Change:** What did you do? (Fix a bug? Add a feature?)
2.  **Determine Impact:** Does it break backward compatibility?
3.  **Format Message:** Construct the header line `type(scope): description`.
4.  **Commit:** Use the formatted message.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [MichaelD-42](https://github.com/MichaelD-42)
- **Source:** [MichaelD-42/agentic-skills](https://github.com/MichaelD-42/agentic-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-michaeld-42-agentic-skills-git-conventional-commits
- Seller: https://agentstack.voostack.com/s/michaeld-42
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.