prowler-commit

To generate conventional commit messages, this Skill formats your git changes into the standard `type(scope): description` structure. It automatically guides scope and type selection, like `feat` or `fix`, to ensure your project history remains consistent and readable.

Conventional commits format structures version control history by enforcing a `type(scope): description` syntax for git commits. Using this standardized format improves code management readability and enables automated changelog generation for your development workflow.

To write a conventional commit with the correct type and scope, this Skill provides guided selection for categories like `feat`, `fix`, or `chore`, and scopes like `api` or `ui`. It enforces character limits and concise descriptions to ensure high readability.

Yes, you can review automated git commit messages before committing because this Skill always prompts for user approval. It generates the structured conventional commit format and waits for your final confirmation to prevent unauthorized or incorrect code changes.

Automated commit formatting directly facilitates changelog generation by enforcing the conventional commits specification. Structuring every git commit with explicit types like `feat` or `fix` allows changelog automation tools to parse project history and extract release notes accurately.