Leavn Commit Machine

VerifiedSafe

Create clean Git commits with emoji prefixes and detailed summaries for the Leavn app.

Sby Skills Guide Bot
DevelopmentBeginner
8/4/2026
Claude Code
#git#commit-messages#commit-convention#workflow#emoji-prefix

Recommended for

Automated summary

Writes and runs git commits that follow the Leavn app's emoji-prefix convention, based on an inspection of the current changes.

Strengths

  • Runs git status, git diff --stat and git diff before drafting the message
  • Ships an explicit emoji taxonomy (fix, feature, cleanup, performance, security, UI, audio, docs)
  • Enforces a structured format: short subject plus bulleted body with file counts, line changes and impact
  • Uses a heredoc so the commit message needs no manual escaping

Limitations

  • Tied to the Leavn app: the emoji prefixes are not reusable as-is in other projects
  • Runs git add -A, staging every modified file without any selection step
  • Always appends the Claude Code / Co-Authored-By footer and covers neither split commits nor pushing or post-commit verification
When to use it

Use it once a batch of changes in the Leavn repository is ready and you need a consistent, readable commit message.

When not to use it

Avoid it on repositories that do not use the Leavn emoji convention, or when you only want to stage specific files.

Security analysis

Safe
Quality score85/100

The skill only runs standard git commands (status, diff, add, commit) via Bash. There is no network access, file deletion outside git staging, secret exfiltration, or obfuscated payloads. While 'git add -A' stages all changes, this is a normal and expected workflow action, not a security risk.

No concerns found

How this analysis is made

Examples

Commit all pending Leavn changes
Use the Leavn Commit Machine to review my current changes and commit them with the right emoji prefix and a detailed message.
Commit an audio feature
I just finished the new playback queue in Leavn. Check the diff and create a commit using the appropriate audio emoji and a short summary of the impact.
Commit a bug fix across several files
Commit my bug fix in the Leavn app: inspect git status and git diff, pick the correct emoji prefix, and write a message with bullet points and file/line counts.

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:

    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 <noreply@anthropic.com>
    
  4. Commit:

    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

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/leavn-commit-machine-mse7io0m/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/leavn-commit-machine-mse7io0m' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/leavn-commit-machine-mse7io0m/download' --output '.skill-downloads/leavn-commit-machine-mse7io0m/SKILL.md.part' && mv '.skill-downloads/leavn-commit-machine-mse7io0m/SKILL.md.part' '.skill-downloads/leavn-commit-machine-mse7io0m/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash, Read

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/leavn-commit-machine-mse7io0m/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills