Automated Release Manager FAQs

Question 1

What happens if a CI workflow fails during the release?

Accepted Answer

The skill monitors GitHub Actions in real-time and will poll the status until completion; if a failure occurs, it retrieves and reports the failed logs directly to the user.

Question 2

Does this skill push code automatically?

Accepted Answer

The skill prepares the release but always requires explicit user confirmation before executing the release command, committing changes, or pushing tags.

Question 3

Can I specify a version manually?

Accepted Answer

Yes, if you specify a version number in your request, the skill will prioritize your input over the automatically calculated version bump.

Question 4

Are uncommitted changes allowed when starting a release?

Accepted Answer

No, the skill checks for a clean working directory and will warn the user and stop if there are uncommitted changes to ensure release integrity.

Question 5

How does the skill determine the next version number?

Accepted Answer

It analyzes the commit history since the last tag using conventional commit patterns to decide if a patch (fix), minor (feat), or major (breaking change) version bump is required.

Automated Release Manager

Key Features

Use Cases

Automated Release Manager

Key Features

Use Cases