yorkie-android-sdk

Cuts and publishes a new version of the yorkie-android-sdk to Maven Central. Runs the full release flow: branch release/vX.X.X from develop, bump VERSION_NAME in gradle.properties, PR to main, create the GitHub Release that triggers publish.yml, then sync main back into develop (and SNAPSHOT / manual publishes via publish-manual.yml). ALWAYS use this skill for ANY request to release, publish, ship, tag, or cut a version of the SDK — including short ones like "release v0.7.5", "ship 0.6.36", "publish to maven central", "cut a release", "re-cut the release", "bump the version and tag it", "get develop out on central sonatype", or "put out a 0.8.0-SNAPSHOT". Don't hand-roll any of this with raw git/gh: the publish is an irreversible Maven Central step and needs a GitHub Release (not a bare tag) to fire publish.yml. NOT for: a normal PR to develop, bumping third-party dependency versions in libs.versions.toml, git-tagging an arbitrary checkpoint, hotfix PRs, or just reading a version number.

Orchestrates Android development tasks including project creation, deployment, SDK management, and environment diagnostics using the `android` command-line tool.

Creates or updates a PR for yorkie-android-sdk with English body and JIRA integration. Auto-detects base branch from current branch name. Supports updating existing PRs. Triggered by "create PR", "make PR", "open PR", "pull request", "push and PR", "update PR", "update PR title", "update PR body".

Bug-fix workflow from JIRA ticket to PR. Fetches the bug report, investigates root cause, writes a failing test (when possible), fixes the bug, and creates a PR. Use this whenever the user wants to fix a bug from a JIRA ticket, e.g. "fix bug 123", "fix-bug-flow 123", "fix-bug-flow RTCOLLABPLATFORM-123", "there's a bug in ticket 123 please fix it", "hotfix 123".

Feature development workflow from JIRA ticket to PR. Fetches the feature request, writes implementation plan, implements with team-review, and creates PR(s). For large features, creates subtask tickets and a base feature branch with sub-PRs. Use this whenever the user wants to implement a new feature from a JIRA ticket, e.g. "new-feature-flow 123", "implement feature 123", "add feature from ticket 123", "work on feature RTCOLLABPLATFORM-123".

Refactoring workflow from JIRA ticket to PR. Fetches the refactoring task, analyzes current code, ensures tests pass before changes, refactors with zero behavior change, and creates PR. Use this whenever the user wants to refactor code from a JIRA ticket, e.g. "refactor-flow 123", "refactor ticket 123", "clean up code for ticket 123", "restructure the code in RTCOLLABPLATFORM-123".

JIRA ticket dispatcher. Fetches the issue, detects the type (bug, feature, refactor, etc.), and routes to the appropriate workflow skill. Use this when the user mentions a JIRA ticket number without specifying a workflow, e.g. "solve 42", "work on ticket 42", "RTCOLLABPLATFORM-42", "what should I do with ticket 123".

Multi-agent review for yorkie-android-sdk. Runs critic-reviewer and test-writer in parallel; adds api-compat-checker when Client, Document, JsonObject/Array/Text/Tree, or .proto files are in the diff; adds protobuf-converter-checker when .proto files are in the diff. Triggered by "team review", "review changes", "review this", "review PR", "code review".

Creates or updates a JIRA issue in the RTCOLLABPLATFORM project. Triggered by "create jira", "create issue", "new ticket", "log a bug", "open a ticket", "update jira", "update issue".

Scans yorkie/ Kotlin files for TODO/FIXME comments. Creates JIRA tickets (RTCOLLABPLATFORM) for actionable items and a GitHub Issue summary. Triggered by "scan todos", "todo scan", "find todos", "check todos".