Conventional Commit Writer

What it does

Reviews staged changes and drafts a commit message following the conventional commits format (type, optional scope, concise description, body when needed). Groups unrelated changes into separate commits when appropriate and never commits or pushes without the developer confirming the message first.

When to use it

• You've made a set of code changes and need a clean, standard-compliant commit message
• You want commits split logically instead of one large catch-all commit
• You maintain a changelog or release process that depends on conventional commit types

Steps

1. Review the diff of staged changes to understand what actually changed
2. Determine the correct type (feat, fix, chore, docs, refactor, etc.) and scope if relevant
3. Draft a concise, imperative-mood summary line within standard length limits
4. Add a body explaining why the change was made if it's not obvious from the diff
5. Split unrelated changes into separate proposed commits instead of combining them
6. Present the drafted message(s) for approval before any commit is actually made

The skill

---
name: conventional-commit-writer
description: Create clear, well-formatted git commits following conventional commit standards, drafted for review before anything is committed.
---

# Conventional Commit Writer

## 1. Overview
Reviews staged changes and drafts a commit message following the conventional commits format (type, optional scope, concise description, body when needed). Groups unrelated changes into separate commits when appropriate and never commits or pushes without the developer confirming the message first.

## 2. When to Use
- You've made a set of code changes and need a clean, standard-compliant commit message
- You want commits split logically instead of one large catch-all commit
- You maintain a changelog or release process that depends on conventional commit types

## 3. Steps
1. Review the diff of staged changes to understand what actually changed
2. Determine the correct type (feat, fix, chore, docs, refactor, etc.) and scope if relevant
3. Draft a concise, imperative-mood summary line within standard length limits
4. Add a body explaining why the change was made if it's not obvious from the diff
5. Split unrelated changes into separate proposed commits instead of combining them
6. Present the drafted message(s) for approval before any commit is actually made

## 4. GoHighLevel Angle
Apply this inside GoHighLevel workflows (funnels, automations, or client reporting) wherever the same task recurs for an agency or client account.

## 5. Safety Rules
- Always produce a draft first; never send, publish, or spend money without explicit human approval.
- Never invent data, metrics, or results — use only what is confirmed or clearly label estimates.
- Never paste API keys, tokens, or passwords into chat; reference secrets by name from a secure store.

For Claude Code, save it as ~/.claude/skills/conventional-commit-writer/SKILL.md. In Cursor, ChatGPT or another assistant, paste it as project instructions.