Automated Release Preparation FAQs

Question 1

How does the skill determine the next version number?

Accepted Answer

The skill analyzes the Git commit history since the last tag and uses conventional commit prefixes (e.g., 'feat:' for minor or 'fix:' for patch) to recommend the appropriate SemVer bump.

Question 2

Can I run this skill in the background?

Accepted Answer

Yes, the skill is specifically designed to run long-running tasks like benchmarks and CI checks in background mode, allowing you to monitor progress via a status table without blocking your workflow.

Question 3

Is it safe to re-run if a step fails?

Accepted Answer

Yes, the underlying scripts are idempotent. If a network timeout or CI delay occurs, you can safely restart the process, and it will skip already completed steps.

Question 4

Does it actually publish the release to GitHub or npm?

Accepted Answer

It handles all preparation phases—including branch creation, PR merging, and note generation—and then provides a final prompt to trigger the actual publishing script once you've reviewed the results.

Question 5

What specialized agents are involved in the review process?

Accepted Answer

It coordinates four specialized agents: a DevOps Engineer for benchmarks, an Architect for documentation accuracy, a Maintainer for code quality/security, and a Developer for verifying runnable examples.

Automated Release Preparation

주요 기능

사용 사례

Automated Release Preparation

주요 기능

사용 사례