release

Cut a semver release for the Medito Flutter app by bumping version, updating release notes, committing, tagging, and pushing.

1.3k|163|Updated Feb 28, 2021
One-click install
npx skills add https://github.com/meditohq/medito-app --skill release-meditohq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/meditohq/medito-app/tree/main/.claude/skills/release
Command: npx skills add https://github.com/meditohq/medito-app --skill release-meditohq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually cutting a new Medito app release requires updating the version, preparing release notes, committing changes, tagging the commit, and pushing to the remote repository, which is error‑prone and time‑consuming.

Core Features & Use Cases

  • Version decision & bump: Determines the next semver version, validates it, and updates pubspec.yaml.
  • Pre‑flight checks: Ensures a clean git state and that the tag does not already exist.
  • Release notes drafting: Invokes the update-release-notes skill to populate the Unreleased section and obtains user approval.
  • Automated script execution: Runs prepare_release.sh, increments the build number, and verifies the changes.
  • Commit, tag, and push: Stages only the relevant files, creates a release commit, tags it, and pushes both branch and tag.

This skill is ideal for developers who need to create a reliable, repeatable release process for the Medito Flutter application.

Quick Start

Ask the release skill to cut a new release for version 3.6.16.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate Flutter app release versioning with git tags and pushes?

To cut a Flutter app release, the process validates the next semver version, updates pubspec.yaml, invokes a release notes skill for approval, runs prepare_release.sh, and commits the git tag to push to origin.

How do I bump the version in pubspec.yaml and prepare release notes for a Flutter app?

Bumping the version in pubspec.yaml requires determining the next semver format and validating it. Release notes are prepared by populating the Unreleased section, obtaining user approval, and incrementing the build number via prepare_release.sh.

What pre-flight git checks are needed before creating a semver release tag?

Before creating a semver release tag, you must ensure a clean git working state and verify that the target tag does not already exist. These pre-flight checks prevent overlapping releases and uncommitted file conflicts.

Does the release automation process work with standard git and shell utilities?

Yes, the release automation process requires only standard git and shell utilities to function. It does not depend on external components or complex environments, making it suitable for standard repository workflows.

How do I commit and push only specific files when cutting a new app release?

When cutting a new app release, the process stages only relevant files like pubspec.yaml and release notes, creates a dedicated release commit, applies the tag, and pushes both the branch and the tag to the remote origin.