commit

Name: commit
Availability: InStock
Author: redwoodog

Create conventional git commit messages from staged or working changes.

174|23|Updated Apr 3, 2026

Search Tags:#automation #git #workflow #commit #lint #version-control #conventional-commits

Ready to run

npx skills add https://github.com/RedWoodOG/Hermes-Desktop --skill commit-redwoodog

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/RedWoodOG/Hermes-Desktop/tree/main/skills/claude-code/commit
Command: npx skills add https://github.com/RedWoodOG/Hermes-Desktop --skill commit-redwoodog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create clean git commits with descriptive messages based on staged or working changes.

Core Features & Use Cases

Guided Commit Messages: Generates clear, conventional messages aligned with project standards.
Staged/Working Changes Handling: Analyzes git status to craft messages that reflect your current work.
Best Practices Enforcement: Suggests subject lines under 72 chars, includes a concise body when needed, and avoids secrets.

Quick Start

Create a concise, conventional commit message for the current changes.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I generate conventional commit messages automatically?▼

To automate conventional commit messages, this Skill analyzes your staged or working git changes and generates structured entries. It enforces conventional commit style, subject length limits under 72 characters, and proper message structure.

What is the best way to keep git commit subject lines under 72 characters?▼

The best way to keep git commit subjects under 72 characters is using a tool that enforces length limits automatically. This Skill suggests concise subject lines and includes a structured body when needed to maintain conventional commit standards.

Can I create git commits from working changes that are not staged yet?▼

Yes, you can create git commits from unstaged working changes. This Skill handles both staged and working changes by analyzing your git status to craft descriptive, conventional commit messages that accurately reflect your current development work.

Does this conventional commit tool check for secrets before committing?▼

Yes, this conventional commit tool avoids secrets during message generation. It enforces best practices by suggesting structured commit messages while actively preventing sensitive data from being included in your automated git workflow.

How do I structure a git commit body for complex changes?▼

Structuring a git commit body for complex changes requires a concise explanation separated from the subject line. This Skill automatically includes a structured body when needed, ensuring your conventional commit message clearly describes the staged or working changes.