What problem does it solve?
Inconsistent Git commit messages and a lack of adherence to conventional commit standards can hinder code review, project history analysis, and automated release processes. This skill automates the creation of consistent, semantic Git commits following Changemaker's conventions.
Core Features & Use Cases
- Conventional Commit Formatting: Guides in constructing commit messages with appropriate types (feat, fix, refactor), scopes, and subjects.
- Detailed Body & Footer: Ensures commits include clear explanations of "what and why" in the body and reference issues or breaking changes in the footer.
- Pre-Commit Validation: Provides a checklist to verify code quality, test status, and documentation updates before committing.
- Use Case: After completing a new feature and passing all tests, use this skill to create your commit. It will help you choose the correct commit type (e.g.,
feat), define the scope, write a concise subject, and include a detailed body explaining the changes, ensuring a clean and informative Git history.
Quick Start
I've added a new API endpoint for challenge enrollment. Stage the relevant files and create a commit with type feat, scope challenge, and a descriptive subject. Reference issue #42.