docs(skills): tighten cut-release resume flow - #172
Closed
stozo04 wants to merge 2 commits into
Closed
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.
Bugbot Autofix prepared fixes for both issues found in the latest run.
- ✅ Fixed: Stop B resume loses build sha
- Added buildSha sidecar file written at Step 4 and read at Step 7 to preserve the exact commit that built the AAB across resume.
- ✅ Fixed: Resume misses unmerged bump work
- Added detection step 7 to handle versionName > latest tag with no bump PR, resuming at Step 2 instead of stalling.
You can send follow-ups to the cloud agent here.
Reviewed by Cursor Bugbot for commit 7c4034e. Configure here.
… bump commits Fixes two bugs in the cut-release skill: 1. Stop B resume loses build sha (medium severity): Detection step 5 now mentions the buildSha sidecar file. Step 4 writes buildSha to releases/openloop-<version>-<code>.buildsha when building. Step 7 reads from this file to ensure the tag points to the same commit that built the AAB, even after resuming. 2. Resume misses unmerged bump work (low severity): Added new detection step 7 to handle versionName > latest tag with no bump PR. This case (Step 1 completed but PR not yet created) now resumes at Step 2 (sweep + create PR) instead of stalling or re-bumping.
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
Verification
Inspect Code was skipped because no Android Studio export was available and this PR changes only skill Markdown. Product builds, emulator verification, and onboarding were skipped by the DocsOnly gate.
Note
Low Risk
Documentation-only changes to agent skill Markdown; no app, script, or release pipeline code changes.
Overview
Updates the cut-release skill (identical copies under
.claude,.codex, and.cursor) so resuming a Play release is stage-aware and less error-prone whenmainmoves after the version-bump PR merges.Stage detection now treats version history and GitHub PR data as authoritative (not
chore/release-*branch names), adds handling for an unmerged local bump, and requires correcting mistaken issue numbers vs PR numbers. Ground-truth docs are loaded only when the current step needs them—especially skippingpre-pr-sweepon post-merge resume.Build SHA replaces the old “bump merge commit only” rule: after merge, the skill must pick the final included merged PR (owner-named cutoff or explicit ask), verify
app/build.gradle.ktsat that SHA, build/tag/notes from that point, and persist it inreleases/openloop-<version>-<code>.buildshafor Stop B / Step 7 resume.Reviewed by Cursor Bugbot for commit f4c57cd. Bugbot is set up for automated code reviews on this repo. Configure here.