release-prepare

Automate VivaDicta release preparation with version bumps and pre-submission checks.

103|6|Updated Aug 2, 2025
One-click install
npx skills add https://github.com/n0an/VivaDicta --skill release-prepare-n0an
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-prepare
Source: https://github.com/n0an/VivaDicta/tree/main/.claude/skills/release-prepare
Command: npx skills add https://github.com/n0an/VivaDicta --skill release-prepare-n0an

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end VivaDicta release preparation tasks to streamline version bumps, metadata updates, and pre-submission checks.

Core Features & Use Cases

  • Create a release/X.Y.Z branch and bump MARKETING_VERSION and CURRENT_PROJECT_VERSION across all targets.
  • Sweep code for TODOs, hardcoded keys, debug statements, and blocked triggers before submission.
  • Generate and manage What's New content, App Store notes, and changelogs across Obsidian and vault sources.

Quick Start

Create a release/X.Y.Z branch and follow the step-by-step flow to bump versions, update metadata, add What's New notes, and finalize App Store assets.

Frequently Asked Questions about release-prepare

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

FAQPage Schema
How do I automate App Store release preparation for version bumps and metadata updates?

App Store release preparation is automated by creating a release branch, bumping MARKETING_VERSION and CURRENT_PROJECT_VERSION across targets, and updating metadata through a structured step-by-step flow.

What is included in pre-submission checks before an App Store release?

Pre-submission checks sweep code for TODOs, hardcoded keys, debug statements, and blocked triggers to ensure the project meets App Store release preparation requirements.

How do I generate release notes and What's New content across Obsidian vault sources?

Release notes and What's New content are generated and managed across Obsidian vault sources as part of the structured release flow to finalize App Store assets.

Does this release preparation workflow require specific dependencies for version bumping?

The release preparation workflow operates without external dependencies, directly applying version bumps and metadata updates across multiple project targets.

What is the best way to manage changelog updates before an iOS App Store submission?

The best way to manage changelog updates is using an automated end-to-end flow that generates App Store notes and synchronizes changes across Obsidian and vault sources.

When should I not use an automated release preparation flow for versioning?

Automated release preparation is not suited for projects outside the VivaDicta ecosystem or those requiring manual, granular control over individual App Store metadata fields.