git-commit

Create conventional Git commits for staged changes with enforced branch naming.

3|3|Updated Jan 18, 2026

Search Tags:#git #workflow #version control #commit #conventional commits #branching

Ready to run

npx skills add https://github.com/CodySwannGT/lisa --skill git-commit-codyswanngt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/CodySwannGT/lisa/tree/main/plugins/lisa/skills/git-commit
Command: npx skills add https://github.com/CodySwannGT/lisa --skill git-commit-codyswanngt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating conventional commits for your code changes, ensuring consistency and clarity in your version control history.

Core Features & Use Cases

Conventional Commits: Enforces a standardized format for commit messages (feat, fix, chore, etc.).
Complete Commit History: Ensures all staged files are included in commits, preventing lost work.
Clean Working Directory: Verifies that the working directory is clean after commits.
Use Case: When you've completed a new feature, use this Skill to automatically stage, commit, and verify your changes according to best practices.

Quick Start

Use the git-commit skill to create a conventional commit for your current changes.

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I automate conventional commits for staged changes?▼

To automate conventional commits, this Skill stages your changes and generates formatted commit messages using types like feat, fix, chore, and docs. It ensures all files are included and verifies the working directory is clean.

What is the conventional commit format for version control?▼

The conventional commit format standardizes version control history by prefixing messages with specific types. Supported types include feature, fix, chore, docs, style, refactor, and test, ensuring clarity and consistency across your branching workflow.

Does this conventional commit tool enforce branch naming conventions?▼

Yes, this conventional commit tool enforces branch naming conventions specifically for development and staging branches. It checks branch names before committing to maintain strict version control workflow standards.

How do I ensure all staged files are included in my git commit?▼

To ensure all staged files are included in a git commit, this Skill automates the process by verifying staged changes and generating a complete conventional commit. It prevents lost work by confirming a clean working directory afterwards.

Can I create a chore commit type for routine maintenance tasks?▼

Yes, you can create a chore commit type for routine maintenance. This Skill supports feature, fix, chore, docs, style, refactor, and test commit types to categorize your version control changes accurately.

What is the best way to maintain a clean working directory after committing?▼

The best way to maintain a clean working directory after committing is to use an automated conventional commit process. This Skill verifies the working directory is clean post-commit, ensuring no staged files are left behind.