reset-version

Reset modified plugin versions to production origin/main patch plus one.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/taptap/agents-plugins --skill reset-version
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reset-version
Source: https://github.com/taptap/agents-plugins/tree/main/.claude/skills/reset-version
Command: npx skills add https://github.com/taptap/agents-plugins --skill reset-version

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the manual and error-prone task of aligning local plugin and marketplace version numbers with the production origin/main versions by computing and applying a patch-level increment for changed plugins before release.

Core Features & Use Cases

  • Detect changed plugins: Combines git diff and untracked file checks to find both tracked and newly added plugin changes under plugins/.
  • Read production versions: Reads marketplace and plugin manifest versions from origin/main to determine the current production release numbers.
  • Compute and update versions: Increments the patch version (production patch +1) and updates only the affected entries in .claude-plugin/marketplace.json, plugins//.claude-plugin/plugin.json, and plugins//.codex-plugin/plugin.json.
  • Use Case: Use this workflow to ensure a consistent, incremental version bump across a plugin marketplace and individual plugin manifests prior to publishing a release.

Quick Start

Run the reset-version skill to fetch origin/main, detect modified plugins including untracked files, compute patch+1 for production versions, and update only the affected marketplace and plugin manifest files.

Frequently Asked Questions about reset-version

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bump plugin versions automatically before a git release?▼

To bump plugin versions before a git release, fetch origin/main, detect modified and untracked plugins under plugins/, then compute a patch increment (production patch +1) and update marketplace.json and plugin.json manifests accordingly.

Can I update marketplace manifest versions for only changed plugins?▼

Yes, marketplace manifest versions can be updated for only changed plugins by combining git diff and untracked file checks to detect modifications, then applying a patch+1 increment solely to affected entries in .claude-plugin/marketplace.json.

How does git versioning work for newly added untracked plugin files?▼

Git versioning for untracked plugin files works by detecting newly added files under plugins/, reading production versions from origin/main, and applying a patch+1 increment to their plugin.json and marketplace.json entries alongside tracked changes.

Do I need to manually read production versions from origin/main to increment plugin versions?▼

No, you do not need to manually read production versions from origin/main. The versioning workflow automatically fetches origin/main, reads existing marketplace and plugin manifest versions, and computes the patch+1 increment for you.

What is the best way to align local plugin versions with production origin/main before publishing?▼

The best way to align local plugin versions with production origin/main is to run an automated versioning workflow that fetches origin/main, detects changed plugins, and applies patch+1 increments to both marketplace and plugin manifests before release.

Why are my plugin manifest versions out of sync with the marketplace manifest?▼

Plugin manifest versions fall out of sync with the marketplace manifest when local changes are made without incrementing versions. Running a reset-version workflow aligns both .claude-plugin/marketplace.json and plugins/*/.claude-plugin/plugin.json to production patch+1.