release

release

Cut a new release of mojoapp-ai/agent-skills. Designed to be run from inside the repo with Claude Code.

Prerequisites

• You are at the repo root: agent-skills/ with skills/, .claude/, README.md, CHANGELOG.md visible.
• Working tree is clean — no uncommitted changes (git status shows nothing).
• gh CLI is logged in for both hanamizuki (default) and mojoapp-ai accounts.

If any of the above fails, stop and tell the user what's wrong.

Step 1 — Inspect what's changed

git fetch --tags
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
if [ -z "$LAST_TAG" ]; then
  echo "No previous tag. This will be the initial release."
  COMMITS=$(git log --pretty=format:"%h %s")
else
  echo "Last tag: $LAST_TAG"
  COMMITS=$(git log "$LAST_TAG..HEAD" --pretty=format:"%h %s")
fi
echo "$COMMITS"

Step 2 — Classify commits and propose a bump

Walk through each commit subject:

Pattern in subject	Category	Bump signal
feat: / feat(...):	Added	minor
fix: / fix(...):	Fixed	patch
docs: / docs(...):	Documentation	patch
chore: / chore(...):	(omit from changelog unless notable)	patch
refactor:	Changed	patch
BREAKING CHANGE: or subject contains !:	breaking	major
anything else	Other	patch

Proposed bump rule:

• Any breaking change present → major (X.0.0)
• Else any feat: present → minor (0.X.0)
• Else → patch (0.0.X)

For pre-1.0 releases (0.x.y), demote one level:

• breaking → minor (0.X.0)
• feat → minor (0.X.0)
• fix/docs → patch (0.0.X)

Show the user the classification + proposed version and ask to confirm before continuing.

Step 3 — Update CHANGELOG.md

Format follows Keep a Changelog.

Insert a new section just below the ## [Unreleased] header (create both if missing). Example for v0.2.0 on 2026-06-15:

## [0.2.0] — 2026-06-15

### Added
- mojo-food-log: support importing fiber-only entries (#42)

### Fixed
- mojo-glp1-knowledge: corrected Wegovy half-life from 7d to 165h

### Documentation
- mojo-app-docs: synced from nextra @ a1b2c3d