skills.rest
wanghaisheng
wanghaishengCOMMUNITY
Explore all skills by this author →
Website𝕏@edwin_uestcGitHub

1k-bundle-release

Automate bundle release workflows on release/* branches with checkout, prepare, diff-check, publish, and sync subcommands.

Updated Apr 15, 2026
Search Tags:#automation#git#workflow#versioning#release#bundle#release-notes
One-click install
npx skills add https://github.com/wanghaisheng/web3-scaffold-app-monorepo --skill 1k-bundle-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 1k-bundle-release
Source: https://github.com/wanghaisheng/web3-scaffold-app-monorepo/tree/main/.claude/skills/1k-bundle-release
Command: npx skills add https://github.com/wanghaisheng/web3-scaffold-app-monorepo --skill 1k-bundle-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Release branch management and automation for bundle releases: it coordinates checkout, build preparation, pre-release diff checks, publishing tracking, and syncing changes back to x.

Core Features & Use Cases

  • Checkout: create release feature branches from the latest release and follow the workflow.
  • Prepare & Diff: set BUILD_NUMBER, run diffs, and generate release notes.
  • Publish & Sync: record releases in RELEASES.json and rebase/sync changes back to x for cross-branch consistency.
  • Use Case: teams releasing App Shell bundles across web/mobile/desktop platforms.

Quick Start

Checkout a new bundle release feature from the latest release branch and follow the on-screen prompts to prepare, diff-check, publish, and sync.

Frequently Asked Questions about 1k-bundle-release

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

FAQPage Schema
How do I automate bundle release workflows on release branches?▼

Automate bundle release workflows on release/* branches by using subcommands like checkout, prepare, diff-check, publish, and sync to ensure consistent pre-release checks, builds, and synchronization back to the main x branch.

How does a release branch diff check work before publishing?▼

Release branch diff checks work by running diffs after setting the BUILD_NUMBER and preparing the build, which generates release notes and validates changes before recording the release in RELEASES.json.

Can I use this for App Shell bundle releases across multiple platforms?▼

Yes, this is specifically applicable to App Shell release cycles where developers create release/* branches to publish tracking and sync changes to x across web, mobile, and desktop platforms.

Do I need a clean working tree to create a release branch?▼

Yes, the workflow enforces a clean working tree before creating and updating RELEASES.json, reading the VERSION from the .env.version file to ensure consistent pre-release state.

What is the best way to sync changes back to the main branch after a release?▼

The best way to sync changes back to the main x branch is using the sync subcommand, which rebases release branch changes to maintain cross-branch consistency after publishing tracking.

Why does my release workflow require reading VERSION from a file?▼

Reading VERSION from the .env.version file is required to accurately set the build number and track the release state within RELEASES.json during the prepare and publish steps.

Related Skills

Explore More Software Engineering Skills→
ruifrvazruifrvaz
3

smaqit.release-prepare-files

Validate Git state and finalize CHANGELOG.md and version files.

Community
Intermediate
flurdyflurdy
6

rebase-main

Rebase the current feature branch onto origin/main with conflict handling and status reporting.

Community
Intermediate
mkrlabsmkrlabs

github-release

Automate GitHub releases with tag validation and build checks.

Official
Advanced
no-problem-devno-problem-dev
5

release-prepare

Update CHANGELOG, validate semantic versioning, and push release branches via Git.

Official
Intermediate