flawed-sample-skill

Conventional commit messages structure git history using a type(scope): subject format, making project history clean and machine-readable for automated semantic versioning. This skill generates these formatted messages based on staged git diffs.

To generate a conventional commit message, run this skill against your staged git changes. It analyzes the file modifications and automatically suggests an appropriate commit type, scope, and subject matching the conventional format.

Yes, this conventional commit generator requires git access to read staged changes. It interprets file modifications to determine semantic context and suggest appropriate commit types like feat, fix, or docs.

Yes, you can use this tool to automate semantic versioning workflows. It generates standardized conventional-commit messages that ensure clean project history and machine-readable commit types required for automated versioning.

The best way to structure commit messages for semantic versioning is using the conventional type(scope): subject format. This skill automatically applies this structure by analyzing staged git diffs and categorizing changes into types like feat or fix.

A limitation of automatically generating conventional commit messages from git diffs is that the semantic context is inferred solely from file modifications. Complex or highly coupled changes may require manual review to ensure the suggested commit type is accurate.