---

name: commit description: Creates atomic git commits with conventional commit messages following standard prefixes (feat, fix, docs, refactor, test, chore, etc.). Stages changes, reviews uncommitted files, and generates properly formatted commit messages. Use when committing code, creating git commits, staging files, or when the user mentions conventional commits or commit messages. license: MIT metadata: author: Yves Tkaczyk version: "0.1"

Git Commit Skill

This skill helps you create well-structured, atomic git commits following conventional commit standards.

What this skill does

• Reviews uncommitted changes in your repository
• Stages the appropriate files for commit
• Generates atomic commit messages with conventional commit prefixes
• Ensures commits follow best practices

When to use this skill

Use this skill when you:

• Need to commit changes to your git repository
• Want to create properly formatted commit messages
• Need help determining which files to stage
• Want to follow conventional commit standards

How to use this skill

1. Review uncommitted changes

   • Run git status to see what files have been modified
   • Run git diff HEAD to review the actual changes
   • Run git status --porcelain for a machine-readable status

2. Stage the changes

   • Add untracked files using git add
   • Stage modified files using git add
   • Ensure only related changes are staged together for atomic commits

3. Create the commit message

   • Use conventional commit format: <type>: <description>
   • Common types include:
     • feat: A new feature
     • fix: A bug fix
     • docs: Documentation changes
     • style: Code style changes (formatting, missing semicolons, etc.)
     • refactor: Code refactoring
     • test: Adding or updating tests
     • chore: Maintenance tasks
     • perf: Performance improvements
     • ci: CI/CD changes
     • build: Build system changes

4. Commit the changes

   • Create an atomic commit that represents a single logical change
   • Ensure the commit message clearly describes what changed and why

Example

Copy# Review changes
git status
git diff HEAD

# Stage changes
git add src/component.ts
git add tests/component.test.ts

# Commit with conventional message
git commit -m "feat: add new component for user profile display"