القائمة
Automates the synchronized Sesori App + Bridge release workflow — bumps versions together and creates a PR
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Update the targeted OpenCode, Codex, and Cursor CLI runtime versions used by the Sesori bridge. Use when asked to update, bump, or refresh the coding backend runtimes, their minimum versions, or their release checksums.
Weekly dependency update workflow for Sesori Apps Monorepo. Updates every pubspec.yaml across the bridge and client workspaces plus standalone packages, regenerates all lockfiles, re-resolves iOS/macOS SwiftPM native dependencies (Package.resolved), updates Fastlane/Gemfile versions, handles conflicts, and verifies via analyze/test/codegen.
Address unresolved inline PR review comments on a GitHub pull request. Fetches unresolved comments, assesses validity (with extra scrutiny for AI/bot reviewers), implements fixes, leaves a reply on every comment thread, and commits changes. Use when the user asks to address PR comments, resolve review feedback, implement requested changes, or handle PR review threads.
Weekly dependency update workflow for Sesori Apps Monorepo. Updates every pubspec.yaml across the bridge and client workspaces plus standalone packages, regenerates all lockfiles, re-resolves iOS/macOS SwiftPM native dependencies (Package.resolved), updates Fastlane/Gemfile versions, handles conflicts, and verifies via analyze/test/codegen.
Monitor GitHub PRs with the pr_monitor tool and handle incoming "[PR Monitor]" reports. Use immediately after raising a PR, when the user asks to monitor/watch a PR, and whenever a "[PR Monitor]" message arrives in the session (CI results, new review comments, merge conflicts, approvals). Requires gh.
Generate a polished, user-facing release-notes markdown file for a requested release (e.g. "do this for v1.1.0"). By default it starts from the existing auto-generated GitHub release notes and post-processes them (re-orders by importance, merges multi-PR efforts, highlights the big items, drops noise) while preserving the "All PRs merged" section verbatim. Alternatively, when the user explicitly says NOT to use the existing notes, it analyzes all commits/PRs merged since the previous release tag and builds the notes from scratch. Writes a RELEASE_NOTES_<version>.md file only — never edits the live GitHub release.
| name | release |
| description | Automates the synchronized Sesori App + Bridge release workflow — bumps versions together and creates a PR |
| compatibility | opencode |
| metadata | {"audience":"maintainers","workflow":"github"} |
This skill automates the synchronized Sesori release process for both App and Bridge. When invoked with a release type (patch, minor, or major), it computes the next shared semantic version and bumps both app and bridge together.
Ask the user:
What type of release is this? Options:
- patch (e.g., 1.0.6 → 1.0.7) — bug fixes, small improvements
- minor (e.g., 1.0.6 → 1.1.0) — new features, backwards compatible
- major (e.g., 1.0.6 → 2.0.0) — breaking changes
If the user does not specify a release type, ask before proceeding.
Alternatively, the user may provide an explicit version: make bump-version VERSION=<version>.
Run the following to find the most recent release tag:
git tag -l "v*" --sort=-v:refname | head -n 1
Run the root version bump command:
make bump-version TYPE=<type>
Or for an explicit version:
make bump-version VERSION=<version>
This updates both bridge and mobile semantic versions while preserving the mobile build number.
Stage the version-bumped files.
Find commits since the last release tag:
git log <previous-tag>..HEAD --oneline
To get diffs for each side:
git diff <previous-tag>..HEAD -- bridge/
git diff <previous-tag>..HEAD -- client/
git log --oneline --name-only <previous-tag>..HEAD
Categorize commits based on their prefixes (used to summarize the PR body):
feat: or feat( → Addedfix: or fix( → Fixedchore: → Changed (or skip unless significant)docs: → Changedrefactor: → ChangedThis repo does NOT use changelog files. Do not create or update any CHANGELOG.md. The categorized commits above are only used to write the PR body in the next step.
Stage the version-bumped files and commit on the current release branch:
git commit -m "chore(release): v<version>"
Use gh to create the PR:
gh pr create \
--title "chore(release): v<version>" \
--body "$(cat <<'EOF'
## Summary
- Bump shared version to v<version>
## Changes
<list the key changes since v<previous>, or "No changes">
EOF
)" \
--base main
make bump-version command updates both bridge and mobile versions together- No changes in that section of the changeloggh CLI (gh auth status)main branch