OPOS: Skill for Claude Code

release-from-changelog

When to use

When cutting a new version release. Replaces the multi-step manual workflow (extract section via awk → check no-existing-release → gh release create --notes-file) with one skill invocation. Canonicalizes the same awk pattern documented in MAINTAINER.md.

Inputs

• version — the release tag, e.g. v0.2.0. Required.
• target_branch — git ref to tag the release against. Default: current branch ($(git rev-parse --abbrev-ref HEAD)).
• repo — owner/name. Default: read from .claude/task-tracking.config.json repo field.

Steps

1. Verify CHANGELOG.md has the version entry. grep -F "## [<version-without-v>]" CHANGELOG.md must return a match. If not, ABORT with message: "no ## [<version>] heading found in CHANGELOG.md".

2. Extract the section to a temp file via the canonical awk pattern from MAINTAINER.md:

   awk '/^## \['"$VERSION_NO_V"'\]/{p=1;print;next} /^## \[/{p=0} /^\[[0-9]/{p=0} p' CHANGELOG.md > /tmp/release-notes-"$VERSION".md
   

   The p=1;print;next clause starts capturing; the /^## \[/{p=0} clause stops at the next version heading; the /^\[[0-9]/{p=0} clause stops at the link-reference block at file bottom.

3. Verify extract non-empty: test -s /tmp/release-notes-"$VERSION".md. If empty (the awk pattern didn't find content), ABORT with "extracted notes empty — check CHANGELOG format".

4. Verify no existing release with this version (INVERTED exit-code logic — gh release view returns 0 when release EXISTS, which we don't want):

   if gh release view "$VERSION" --repo "$REPO" > /dev/null 2>&1; then
     echo "ERROR: release $VERSION already exists" >&2
     exit 1
   fi
   

5. Pre-release scaffold check (added v0.3.1; auto-install dev-deps added v0.7.2). Before tagging, verify the working tree scaffolds cleanly via Copier. First, ensure pinned Python dev-deps are installed — this catches the v0.7.0 + v0.7.1 fresh-machine failure mode where copier itself was missing/broken:

   # v0.7.2: ensure dev-deps are pinned/installed BEFORE the scaffold check.
   # Prevents the "copier missing on fresh machine" failure mode that skipped
   # the v0.7.0 + v0.7.1 scaffold checks. Warn-and-continue on pip failure so
   # the release pipeline isn't held hostage by a broken pip.
   pip install --quiet -r "$REPO_ROOT/requirements-dev.txt" || {
     echo "WARNING: pip install -r requirements-dev.txt failed. Falling back to"
     echo "         best-effort scaffold check (may also fail). Investigate after."
   }
   
   rm -rf /tmp/opos-prerelease-check
   python3 -m copier copy . /tmp/opos-prerelease-check \
     -d COMPANY_NAME=PreReleaseCheck --defaults --vcs-ref=HEAD
   rm -rf /tmp/opos-prerelease-check
   

   Assert exit 0. This catches Copier-side breakage (renamed templates, missing _skip_if_exists, stray .jinja files that shouldn't be templated, etc.) BEFORE the release is tagged. If this fails, ABORT — fix the scaffolding issue and re-run; do NOT proceed. Rationale: v0.3.0's first cut shipped broken templates because ui/templates/*.html.jinja files were being rendered by Copier instead of shipped verbatim, requiring a destructive delete-and-re-cut. This step would have caught it.