agentleFS
Namma-FlutterNamma-Flutter/namma_wallet/.agents/skills/release-updater/SKILL.md

release-updater

Skill59 starsChanged 5 months agoMITView on GitHub

Automates bumping the app version, updating the technical CHANGELOG.md, and updating the App Store & Play Store release notes in a user-friendly way. Make sure to use this skill whenever the user mentions releasing a new version, bumping the app version, updating changelogs, or preparing metadata files for App Store/Play Store.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run git log <last-version-commit>..HEAD (or scan from the commit that last bumped the version, e.g.

    line 15
  2. Very specific:

    Update pubspec.yaml to bump the version.

    line 18
  3. Distinctive:

    Keep the descriptions technical, concise, and accurate to the commits.

    line 31
  4. Distinctive:

    Keep the styling consistent with standard "What's New" bullet points.

    line 40
  5. Distinctive:

    Run the project's data policy script to check for violations:

    line 43
  6. Distinctive:

    Run Flutter static analysis to ensure no compiling issues exist:

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Release Updater

This skill guides the agent through bumping the version and updating all release metadata files in the project.

Workflow

1. Identify the Current Version and Commits

  • Locate the current version in pubspec.yaml.
  • Identify the last released version. This is usually the latest version header documented in CHANGELOG.md (e.g., [0.3.3+9]).
  • Run git log <last-version-commit>..HEAD (or scan from the commit that last bumped the version, e.g. finding the commit where version was changed, or using git log tags) to get all commits that have occurred since the last release.

2. Bump the App Version

  • Update pubspec.yaml to bump the version.
  • Determine the new version number (e.g., increment the patch/minor version and the build number, like 0.3.4+10 -> 0.3.5+11).

3. Update the Technical Changelog

  • Open CHANGELOG.md.
  • Insert a new section for the bumped version right under ## [Unreleased].
  • Format the version header as ## [version] - YYYY-MM-DD (e.g. ## [0.3.5+11] - 2026-06-22).
  • Group the scanned commits into standard changelog sections:
    • ### Added for new features.
    • ### Fixed for bug fixes.
    • ### Changed for refactors/changes to existing features.
    • ### Removed for deprecated/removed features.
    • ### Chores for dependency bumps, configuration updates, and workspace housekeeping.
  • Keep the descriptions technical, concise, and accurate to the commits.

4. Update App Store and Play Store Release Notes

  • Locate the platform release notes:
    • Play Store: default.txt
    • App Store: release_notes.txt
  • IMPORTANT: Release notes must be user-friendly and non-technical. Avoid technical jargon, implementation details, internal field names, or developer-specific terms.
  • Summarize the new version changes in a non-technical, user-friendly way that focuses on user-visible improvements and benefits.
  • Maintain a strict limit of under 500 characters to fit Play Store limitations.
  • Keep the styling consistent with standard "What's New" bullet points.

5. Validate the Workspace

  • Run the project's data policy script to check for violations:
    bash scripts/check_no_default_values.sh
  • Run Flutter static analysis to ensure no compiling issues exist:
    rtk fvm flutter analyze

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.