메뉴
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".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | create-jira |
| description | 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". |
| argument-hint | [--title title] [--type task|bug|epic|subtask] [--fix-version vX.X.X] [--relates-to N] [--epic N] [--parent N] [--update N] [--description text] |
Creates or updates an issue in the RTCOLLABPLATFORM JIRA project.
API reference: .claude/reference/jira-confluence-api.md
| Type | Flag | Max scope |
|---|---|---|
| Task | task (default) | Up to 2 weeks |
| Bug | bug | — |
| Epic | epic | Up to 3 months |
| Subtask | subtask | Up to 2 days |
Parse flags:
--title: Issue summary (required for new issues)--type: task (default), bug, epic, subtask--fix-version: Release version name (e.g. v0.6.36)--relates-to: Issue number to link (e.g. 42 → RTCOLLABPLATFORM-42)--epic: Epic key to link this task under--parent: Parent issue key for subtasks (required when --type subtask)--update: Existing issue number to update (triggers update mode)--description: Issue description textAny numeric-only value for --relates-to, --epic, --parent, --update is auto-prefixed with RTCOLLABPLATFORM-.
If required arguments are missing, ask with AskUserQuestion (always provide options, not free text).
curl -s -H "Authorization: Bearer $JIRA_PERSONAL_TOKEN" \
"https://jira.navercorp.com/rest/api/2/myself" \
-o /tmp/jira-myself.json
Use the name field as the assignee.
If --fix-version is specified, fetch project versions and find the matching name.
If not found, create it:
curl -s -X POST -H "Authorization: Bearer $JIRA_PERSONAL_TOKEN" \
-H "Content-Type: application/json" \
-d '{"name": "{version}", "project": "RTCOLLABPLATFORM", "released": false}' \
"https://jira.navercorp.com/rest/api/2/version" \
-o /tmp/jira-version.json
--update not specified)Always prepend [Android] to the summary title before submitting.
Build the fields object:
{
"project": {"key": "RTCOLLABPLATFORM"},
"summary": "[Android] {title}",
"issuetype": {"name": "{Task|Bug|Epic|Sub-task}"},
"assignee": {"name": "{myself.name}"},
"description": "{description}"
}
Additional fields by condition:
--fix-version → add "fixVersions": [{"id": "{versionId}"}]--type epic → add "customfield_213535": "{title}" (Epic Name)--epic → add "customfield_213534": "RTCOLLABPLATFORM-{N}" (Epic Link)--type subtask + --parent → add "parent": {"key": "RTCOLLABPLATFORM-{N}"}curl -s -X POST -H "Authorization: Bearer $JIRA_PERSONAL_TOKEN" \
-H "Content-Type: application/json" \
-d '{"fields": {...}}' \
"https://jira.navercorp.com/rest/api/2/issue" \
-o /tmp/jira-created.json
If --relates-to is specified, create an issue link after creation.
--update specified)GET /rest/api/2/issue/RTCOLLABPLATFORM-{N}PUT /rest/api/2/issue/RTCOLLABPLATFORM-{N} with the update payload.RTCOLLABPLATFORM-{N}: {title}
Type: {Task|Bug|Epic|Subtask}
Fix version: {version or none}
Relates to: {key or none}
URL: https://jira.navercorp.com/browse/RTCOLLABPLATFORM-{N}
On API failure: print the error and stop.
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".