What problem does it solve?
Manually writing git commit messages that match a repository's established format is time-consuming and prone to inconsistency, making project history hard to navigate and audit.
Core Features & Use Cases
- Conventional Commit Formatting: Automatically generates commit messages that follow the repository's existing style, with a conventional commit type prefix and structured body grouped by change category.
- Safe File Staging: Stages only relevant modified files, automatically excluding secrets, build artifacts, IDE workspace files, and other non-commitable content.
- Use Case: After fixing a batch of compiler warnings across multiple source files in the openRender repository, this skill will generate a properly formatted commit that groups changes by warning type, matches the repo's existing commit style, and stages only the modified source files without including build outputs.
Quick Start
Use the commit-message skill to stage your recent code changes and create a properly formatted git commit that matches this repository's established message style.