Plugin Version Manager FAQs

Question 1

Does it automatically commit the version changes?

Accepted Answer

No, the skill only performs the file edits in plugin.json and marketplace.json, leaving the final commit to the developer for review.

Question 2

How is the bump level (patch, minor, major) determined?

Accepted Answer

The skill analyzes the nature of the changes—such as bug fixes for patches, new features for minor updates, or breaking changes for major releases—and defaults to patch if the level is ambiguous.

Question 3

Can I use this for non-plugin projects?

Accepted Answer

While optimized for projects using plugin.json and marketplace.json structures, the logic can be adapted for any multi-manifest repository requiring synchronized versioning.

Question 4

How does the skill detect which plugins to bump?

Accepted Answer

The skill runs Git diff commands to check for uncommitted changes, cached changes, or modifications in the most recent commit within specific plugin directories.

Question 5

What happens if a plugin is missing from the marketplace file?

Accepted Answer

If a plugin exists in the directory but cannot be found in marketplace.json, the skill will issue a warning to the user rather than stopping the process.

Plugin Version Manager

주요 기능

사용 사례

Plugin Version Manager

주요 기능

사용 사례