菜单
Consolidates ticket claiming operations (assign, transition, add to sprint, track) into a single efficient operation, reducing ~10 tool calls per new-work cycle
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | claim-ticket |
| description | Consolidates ticket claiming operations (assign, transition, add to sprint, track) into a single efficient operation, reducing ~10 tool calls per new-work cycle |
| when_to_use | Invoke when claiming a new JIRA ticket. Triggers on: "claim ticket", "assign ticket", "pick up work", "start new ticket". Replaces manual jira_update_issue + jira_transition + jira_add_issues_to_sprint + task_add calls. |
| user-invocable | true |
| allowed-tools | ["Bash(python3 .claude/skills/claim-ticket/scripts/claim_ticket_operations.py *)","Read"] |
Execute the claim-ticket workflow after selecting a ticket:
python3 .claude/skills/claim-ticket/scripts/claim_ticket_operations.py RHCLOUD-12345 2>&1
Use --dry-run to preview without executing:
python3 .claude/skills/claim-ticket/scripts/claim_ticket_operations.py RHCLOUD-12345 --dry-run 2>&1
The script executes 8 operations in sequence:
All operations use fail-fast error handling: if any operation fails, execution stops immediately.
Set these environment variables:
# JIRA MCP Server (required)
export JIRA_MCP_URL=http://proxy:8090
# Bot JIRA identity (required) — email of the bot's Jira service account (from Vault)
export BOT_JIRA_EMAIL=<your-bot-jira-email>
# Memory Server (required)
export BOT_MEMORY_URL=https://memory-server.example.com
# Board Configuration (one of these required for sprint assignment)
# WARNING: These are EXAMPLES — use your instance's actual board ID/name.
# Using wrong board IDs overwrites the ticket's existing sprint.
export BOT_BOARD_ID=<your-board-id> # Direct board ID (skips lookup)
export BOT_BOARD_NAME="<Your Board Name>" # Lookup board by name via Jira
JIRA operations use MCP via jira_call(). No API tokens needed - the mcp-atlassian server handles authentication. Bot identity for ticket assignment comes from BOT_JIRA_EMAIL.
Memory server operations use direct HTTP (POST /tasks).
Resolves board from environment variables (same as new-work skill):
BOT_BOARD_ID set → use directly (fast path, no API call)BOT_BOARD_NAME set → lookup via jira_get_agile_boardsFail-fast approach: if any operation fails, execution stops immediately and reports the error.
Consolidates post-PR-creation bookkeeping (task updates, JIRA transitions, Slack notifications, learning storage) into a single efficient operation
Slack daily digest management. Send daily digest of queued notifications or trigger a status update for a specific ticket. Routes through memory-server MCP for deduplication and digest support.
Send Slack notification. Reads SLACK_WEBHOOK_URL from env, calls memory-server MCP slack_notify w/ webhook_url. No-ops if webhook not configured.
Post-merge bookkeeping for completed PRs. Archives task, transitions Jira to "Release Pending", posts Jira comment, sends Slack notification, deletes bot branches (remote + local). Handles already-deleted branches gracefully.
Auto-fork repos + update config. Scans project-repos.json for missing forks → forks via gh/glab → updates config → commits.
Consolidates git push and PR/MR creation into a single efficient operation, eliminating 5-8 wasted tool calls per implementation cycle