Promptles
Output Format

Version Every Change

Bump the version for every release, by its effect on users, with a changelog entry. No bump means no update.

Once a plugin has a version number, people only get an update when that number changes, so an unbumped change never reaches them. Bump it by what the change does to users: a patch for fixes, a minor for new features, a major when something they rely on (a command name, an argument) changes. Ask for the changelog entry in the same step. Vague: "Push the rename to the team." Specific: "Renaming /shipkit:notes to /shipkit:release-notes breaks people's habits, so bump 1.4.2 to 2.0.0, add a CHANGELOG entry with upgrade notes, and show me claude plugin validate passing."

Where you'll practice this

One Promptles scenario teaches this principle directly.

  • Release the Fix and the Rename

    Two weeks ago Dana merged a fix so the lint hook stops skipping files with spaces in their names, yet teammates still see the old behavior after restarting Claude Code and updating the marketplace. Since then a second PR renamed the `notes` skill to `release-notes` and dropped…

Other principles in Output Format