RE

repo-prepare-release

Analyzes changelogs and code to automate version bumps and file updates during releases.

Install

mkdir -p .claude/skills/repo-prepare-release && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6697" && unzip -o skill.zip -d .claude/skills/repo-prepare-release && rm skill.zip

Installs to .claude/skills/repo-prepare-release

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Prepare releases by analyzing changelogs, determining version bumps, and updating package.json and changelog files.
115 charsno explicit “when” trigger
Beginner

Key capabilities

  • Scan changelogs for unreleased changes
  • Determine version bump types based on prefix rules
  • Update package.json version fields
  • Update changelog headers and dates

How it works

The skill analyzes changelog files for specific prefixes to determine if a version bump should be minor or patch, then updates metadata files accordingly.

Inputs & outputs

You give it
Repository with unreleased changelog entries
You get back
Updated package.json and CHANGELOG.md files

When to use repo-prepare-release

  • Determine version bumps for releases
  • Automate package.json version updates
  • Generate release changelogs

About this skill

Prepare Release

Packages to Check

Scan these for unreleased changes (placeholder: ## vX.X.X (Month DD, YYYY)):

  • packages/core/CHANGELOG.md and packages/methods/CHANGELOG.md
  • frameworks/{angular,preact,qwik,react,react-native,solid,svelte,vue}/CHANGELOG.md

Version Bump Rules

PrefixBumpExamples
Add, Change (API), RenameMinorNew feature, API change, renamed export
Fix, Change @formisch/*PatchBug fix, dependency update

Release Process

1. Process in Order

  1. @formisch/core → 2. @formisch/methods → 3. All frameworks

2. For Each Package with Changes

Update package.json: Bump "version" field

Update CHANGELOG.md:

  • Replace ## vX.X.X (Month DD, YYYY) with actual version and date
  • Date format: Month DD, YYYY (e.g., January 31, 2026)

3. Framework Dependency Updates

Core/methods are bundled per framework target (/react, /solid, etc.):

  • Framework-specific changes → update only that framework
  • Shared changes → update all frameworks
  • Bump matches core/methods (minor→minor, patch→patch)

Add to affected changelogs:

- Change `@formisch/core` to vX.X.X
- Change `@formisch/methods` to vX.X.X

Checklist

  • Identify all packages with unreleased changelog entries
  • Determine bump type (patch/minor) for each
  • Add dependency update entries to framework changelogs
  • Update all package.json versions
  • Update all changelog version headers and dates
  • Run pnpm check-versions to verify consistency

When not to use it

  • When repository does not follow the specified changelog format

Limitations

  • Requires specific changelog header format
  • Limited to predefined package structure

How it compares

It automates versioning based on specific changelog prefixes rather than manual version incrementing.

Compared to similar skills

repo-prepare-release side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
repo-prepare-release (this skill)15moNo flagsBeginner
bazel-build-optimization142moNo flagsAdvanced
github-workflow-automation112moReviewAdvanced
wolf-scripts-core59moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by open-circle

View all by open-circle

repo-website-api-create

open-circle

Create new API reference pages for the Valibot website at website/src/routes/api/. Use when adding documentation for new schemas, actions, methods, or types. Covers reading source code, creating properties.ts and index.mdx files, updating menu.md, and cross-referencing related APIs.

26

repo-source-code-document

open-circle

Write JSDoc comments and inline documentation for Valibot library source code in /library/src/. Use when documenting schemas, actions, methods, or utilities. Covers interface documentation, function overloads, purity annotations, inline comment patterns, and terminology consistency.

14

repo-source-code-review

open-circle

Review pull requests and source code changes in /library/src/. Use when reviewing PRs, validating implementation patterns, or checking code quality before merging. Covers code quality checks, type safety, documentation review, test coverage, and common issues to watch for.

12

repo-structure-navigate

open-circle

Navigate the Valibot repository structure. Use when looking for files, understanding the codebase layout, finding schema/action/method implementations, locating tests, API docs, or guide pages. Covers monorepo layout, library architecture, file naming conventions, and quick lookups.

16

repo-website-api-update

open-circle

Update existing API documentation pages after source code changes. Use when syncing docs with library changes like new parameters, type constraint changes, interface updates, or function renames. Covers common change patterns and verification steps.

13

repo-website-guide-create

open-circle

Create conceptual documentation and tutorial pages for the Valibot website at website/src/routes/guides/. Use when adding guides about schemas, pipelines, async validation, migration, or other topics. Covers directory structure, MDX templates, frontmatter, and content guidelines.

16

Search skills

Search the agent skills registry