code-payments

Use when the user wants to trigger an Xcode Cloud build for the current branch, kick off the "Deploy Flipcash" workflow, ship an ad-hoc / dogfood build, or push a branch build to a TestFlight group — anything short of a versioned release (for cutting a version, use /release instead).

Fetch latest protobuf definitions, regenerate Swift bindings, verify the build, summarize API changes, and scaffold new service stubs. Usage: /fetch-protos [core|payments] [both]

Daily Bugsnag triage ritual — surface the top open production issue, investigate with evidence, propose a fix direction, route through experts, write a lean review brief.

Build, install, and drive Flipcash on the iPhone 17 simulator to observe a change at its real surface — login deeplink, coordinate-scale gotchas, and chat/send flow routes included.

Use when the user wants to cut a release, ship a version, prepare for release, or invokes /release

Write a reflection about a situation that got out of hand during this session

Look up the git commit and GitHub Actions run for a Flipcash versionCode. Usage: /build-lookup <versionCode>

Download and use the R8 mapping file for a Flipcash release build to deobfuscate stack traces. Usage: /r8-mapping <versionCode>

Triage a Bugsnag production issue — either the top open issue or a specific issue by URL/ID. Investigate with evidence from stack traces / logs / breadcrumbs, propose a fix direction, route through domain experts, and write a lean review brief.

Review a Dependabot PR for breaking changes, gotchas, and required code updates. Usage: /dep-review <PR number or URL>

Fetch latest protobuf definitions, verify build, summarize API changes, and scaffold new service stubs. Usage: /fetch-protos [flipcash|opencode] [commit_sha]

Generate GitHub release notes from git refs (tags, commits, or HEAD). Usage - /release-notes <from> <to>. Runs the changelog script, then rewrites the output into polished GitHub release notes.