git-commit

Stage relevant files and create conventional Git commits with branch safety checks.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/Levezze/devkit --skill git-commit-levezze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/Levezze/devkit/tree/main/skills/git-commit
Command: npx skills add https://github.com/Levezze/devkit --skill git-commit-levezze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes agents (resource) components.

What problem does it solve?

It prevents inconsistent, messy Git commit messages by standardizing commits to a conventional format while avoiding bot-style watermarks.

Core Features & Use Cases

  • Conventional commit message formatting: Automatically detects and applies the project’s commit convention to produce professional messages.
  • Staging and atomic commits: Adds relevant files to staging and creates focused, logical commits instead of dumping everything at once.
  • Branch protection guardrails: Blocks commits to protected branches (main, demo, production) unless the user explicitly requests it.
  • Watermark/bot attribution avoidance: Ensures commit messages are written without AI watermarks or bot attributions.

Quick Start

Ask the AI to use the git-commit skill to add your changes and create a conventional commit for your current branch.

Frequently Asked Questions about git-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write conventional commit messages without bot-style watermarks?

To create conventional commit messages without bot watermarks, the git-commit skill standardizes Git commit creation by detecting the project convention, staging relevant files, and generating professional messages with clear 'why' explanations.

How do I create atomic commits that follow my project's existing commit convention?

Atomic commits are created by detecting diff and status-based changes, staging only relevant files, and generating a convention-compliant professional commit message instead of dumping all changes at once.

Can I use automated Git commits without accidentally pushing to protected branches?

Yes, automated Git commits include branch safety checks that block commits to protected branches like main, demo, and production unless explicitly requested, ensuring guardrails prevent accidental source control updates.

What is the best way to automate staging relevant files for version control commits?

The best way to automate staging is using diff and status-based change detection, which adds only relevant files to staging to create focused, logical commits rather than dumping everything at once.

Why should I avoid bot-style watermarks in commit messages for source control workflows?

Avoiding bot-style watermarks ensures source control workflows maintain professional, convention-compliant logs that provide clear 'why' explanations without AI attributions polluting the Git history.