Conventional Commit Manager FAQs

Question 1

Are the scopes customizable?

Accepted Answer

The skill provides a standard set of scopes like lib, builder, and version, but it is designed to be flexible for any project-specific domain required by your repository.

Question 2

Does this work with rhusky?

Accepted Answer

Yes, it is specifically designed to work alongside rhusky git hooks to ensure commits are valid before they are even processed by the local repository.

Question 3

What is the benefit of using the Conventional Commit skill?

Accepted Answer

It ensures all team members follow the same commit format, making the project history readable and enabling automatic changelog generation via tools like Cocogitto.

Question 4

Does it support multi-line commit messages?

Accepted Answer

Yes, the skill supports full commit bodies and footers for complex changes, ensuring the entire message remains compliant with Angular standards.

Question 5

How do I indicate a breaking change using this skill?

Accepted Answer

To indicate a breaking change, add an exclamation mark before the colon in the commit header, for example: feat(api)!: remove deprecated endpoint.

Conventional Commit Manager

Key Features

Use Cases

Conventional Commit Manager

Key Features

Use Cases