version-updates | sanctum | ClaudePluginHub

Skill

Community

version-updates

11

Description

Bump project versions across configs, docs, and changelog using git-workspace-review context. Triggers: version bump, semver, release version, changelog update, version update, package version, release preparation Use when: bumping project versions, updating changelogs, preparing releases, coordinating version changes across files DO NOT use when: just documentation updates - use doc-updates. DO NOT use when: full PR preparation - use pr-prep. Use this skill for version management and release preparation.

Install

1

Add the repository(one-time)

$

/plugin marketplace add athola/claude-night-market

2

Install the plugin

$

/plugin install pensive@claude-night-market

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Skill Content

Version Update Workflow

When to Use

Use this skill when preparing a release or bumping the project version. Run Skill(sanctum:git-workspace-review) first to capture current changes.

Required TodoWrite Items

version-update:context-collected
version-update:target-files
version-update:version-set
version-update:docs-updated
version-update:verification

Step 1: Collect Context (`context-collected`)

Confirm which version to apply (default: bump patch).
If the prompt provides an explicit version, note it.
Ensure Skill(sanctum:git-workspace-review) has already captured the repository status.

Step 2: Identify Targets (`target-files`)

List configuration files that store the version (e.g., Cargo.toml, package.json, pyproject.toml).
Include changelog and README references that mention the version.

Step 3: Update Versions (`version-set`)

Update each target file with the new version.
For semantic versions, follow MAJOR.MINOR.PATCH or the specified format.
If the project supports multiple packages, document each update.

Step 4: Update Documentation (`docs-updated`)

Add or update changelog entries with today's date.
Refresh README and docs references to mention the new version and any release notes.

Step 5: Verification (`verification`)

Run relevant builds or tests if version bumps require them (e.g., cargo test, npm test).
Show git status -sb and git diff excerpts to confirm the version bumps.

Output Instructions

Summarize the files changed and the new version number.
Mention follow-up steps, such as publishing or tagging, if applicable.

Links

GitHub Stats

2 forks

Similar Skills

Agent Development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

47.1k

Command Development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

47.1k

Hook Development

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

47.1k