home / skills / willsigmon / sigstack / leavn-commit-machine

leavn-commit-machine skill

safe

/plugins/app-dev/skills/leavn-commit-machine

This skill generates clean, descriptive git commits with emoji prefixes and detailed summaries to improve project history.

npx playbooks add skill willsigmon/sigstack --skill leavn-commit-machine

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.3 KB

---
name: Leavn Commit Machine
description: Create clean, descriptive git commits for Leavn app following emoji prefix convention with comprehensive change summaries
allowed-tools: Bash, Read
---

# Leavn Commit Machine

## Instructions

Create commits following Leavn's emoji convention:

1. **Check what changed**:
   ```bash
   git status
   git diff --stat
   git diff
   ```

2. **Choose emoji prefix**:
   - 🔧 `:wrench:` - Bug fixes, corrections
   - 🚀 `:rocket:` - New features, major improvements
   - 🧹 `:broom:` - Code cleanup, deletions
   - ⚡️ `:zap:` - Performance improvements
   - 🛡️ `:shield:` - Security, error handling
   - 🔀 `:twisted_rightwards_arrows:` - Merge, consolidation
   - 🐛 `:bug:` - Bug fixes (visual/functional)
   - 🎨 `:art:` - UI/UX improvements
   - 🎵 `:musical_note:` - Audio features
   - 📝 `:memo:` - Documentation

3. **Write commit message**:
   ```
   {emoji} Brief summary (50 chars)

   - Bullet point details
   - File counts, line changes
   - Impact statement

   🤖 Generated with Claude Code
   Co-Authored-By: Claude <[email protected]>
   ```

4. **Commit**:
   ```bash
   git add -A
   git commit -m "$(cat <<'EOF'
   Message here
   EOF
   )"
   ```

Use this skill when: Ready to commit changes, multiple files modified, need good commit message

Overview

This skill generates clean, descriptive git commits for the Leavn app using the project's emoji prefix convention. It produces a concise header, a short detailed body with file/line change notes and impact statements, and a standard footer that includes generation metadata. The output is formatted for direct use with a shell heredoc commit command to ensure consistent history.

How this skill works

The skill inspects git status and diffs to summarize what changed, then selects the appropriate emoji prefix based on change type (feature, bug, cleanup, etc.). It builds a two-part commit message: a one-line summary under 50 characters and a bulleted body with specifics like file counts, line changes, and impact. Finally it emits the exact commit payload wrapped for use with git add and a heredoc commit command.

When to use it

You have staged or unstaged changes and want a single, clear commit
Multiple files changed and you need to describe scope and impact
Preparing commits for code review or a shared branch
Enforcing Leavn's emoji-based history convention
Automating commit messages in pre-commit workflows

Best practices

Run git status and git diff --stat to understand scope before committing
Pick the emoji that best represents the primary intent of the change
Keep the summary under 50 characters and use bullets for details
Include file counts, notable line changes, and a short impact line
Use the provided heredoc commit pattern to avoid quoting issues

Example use cases

Fixing a UI bug: choose 🐛, summarize the fix, list affected components and visual impact
Adding a new feature: pick 🚀, note new files and API surface, mention migration steps
Refactoring code: use 🧹, enumerate deleted files and reduced complexity
Performance tuning: select ⚡️, report benchmarks and affected modules
Updating docs: use 📝 and list sections updated and reader impact

FAQ

Can I customize the emoji list?

Yes. Use the emoji that matches your team's convention; ensure the commit body remains structured.

What if multiple change types apply?

Prefer the primary intent of the commit. For mixed changes, choose the most impactful emoji and clarify other types in the body.

How do I run the commit safely from the shell?

Stage changes with git add -A, then use the provided heredoc pattern to pass the multi-line message to git commit.