メニュー
Jira operations — sprint board, my issues, create/update/close/link issues. Triggers on sprint, issues, create, update, close, link, or any ACM-xxx mention.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Install and configure Hysteria 2 — either a CLIENT on macOS (Homebrew binary, config, shortcut commands like hy2start/hy2stop/hy2log/proxyon, optional launchd service) or a SERVER on a Linux VPS over SSH (official installer, self-signed cert, systemd service, firewall, prints client credentials). Ask the user server-vs-client first. Use this skill when the user mentions hysteria2, hy2, proxy client/server setup, deploying a Hysteria2 server, or connecting to a Hysteria2 proxy on a new Mac.
Full macOS development environment bootstrap — orchestrates Homebrew, ZSH, Vim/Neovim, tmux, Git+gh, Ghostty, Hysteria2, and macOS preferences. Supports interactive multi-select. Use this skill when the user wants to set up a new Mac, configure a new machine, bootstrap a development environment, or run a full macOS setup.
Install and configure Shadowsocks — either a CLIENT on macOS (shadowsocks-rust sslocal, config, shortcut commands like ssstart/ssstop/sslog/sson, optional launchd service) or a SERVER on a Linux VPS over SSH (shadowsocks-rust ssserver, systemd service, firewall, prints ss:// link + credentials). Ask the user server-vs-client first. Use this skill when the user mentions shadowsocks, ss, sslocal, ssserver, deploying a shadowsocks server, or connecting to a shadowsocks proxy on a new Mac.
Install and configure a sing-box proxy client on macOS — one client that speaks BOTH Hysteria2 and Shadowsocks and switches between them. Installs binary via Homebrew, deploys a merged config, adds shortcut commands (sbstart, sbstop, sblog, sbstatus, sbrestart, sbedit, sbnode, sbon, sboff), and OPTIONALLY sets up a launchd auto-start service (asks the user first). Use this skill when the user mentions sing-box, singbox, a unified proxy client, switching between hysteria2 and shadowsocks, or wants one client for multiple protocols on a new Mac.
Install and configure Zsh with Oh My Zsh, plugins, powerlevel10k theme, and modern CLI tools. Writes a self-contained ~/.zshrc with no external file dependencies. Use this skill when the user mentions setting up zsh, configuring zsh, installing oh-my-zsh, zsh setup, zsh plugins, shell setup, or wants to set up their shell environment on a new machine.
Git workflow automation - commit/push with sign-off, create/list/compact/rebase PRs, and contribute to upstream repos. Use this skill whenever the user mentions PR, pull request, create PR, show my PRs, list PRs, squash commits, compact commits, rebase PR, commit and push, push updates, push changes, contribute to a repo, fork and submit, or wants to manage any aspect of Git operations.
| name | jira |
| description | Jira operations — sprint board, my issues, create/update/close/link issues. Triggers on sprint, issues, create, update, close, link, or any ACM-xxx mention. |
| allowed-tools | ["Bash","Read","Write","Edit","Grep","Glob","WebFetch"] |
Bundled scripts for common Jira workflows. Each operation is a single script call.
Scripts are at ${CLAUDE_SKILL_DIR}/scripts/.
scripts/sprint.sh [board_id]
Outputs a markdown table directly, grouped by status (New -> In Progress -> Closed) with columns: Type, Pri, Key (markdown links), Title, SP, Activity, Components, Versions, Labels. Print the output as-is. Collapse bulk CVE vulnerabilities into a summary row.
scripts/issues.sh [extra_jql_filter]
Lists all issues assigned to current user, excluding Closed and Backlog by default. Supports optional extra JQL filter (e.g. "project = ACM", "component = 'Global Hub'").
Outputs a markdown table directly, grouped by status (New -> In Progress -> Resolved) with columns: Type, Pri, Key (markdown links), Title, SP, Activity, Components, Versions. Keys prefixed with pin emoji indicate issues in the current active sprint. Print the output as-is. Collapse bulk CVE vulnerabilities into a summary row.
scripts/create.sh "<summary>" [type=Task] [priority=Major] [sp=3] [parent=ACM-xxx] [component=Global Hub] [sprint=current] [activity=Product / Portfolio Work]
Defaults: project=ACM, component=Global Hub, assignee=current user, type=Task.
When creating an issue, always ask the user to select an Activity Type using AskUserQuestion (optional — user can skip). Valid values: Product / Portfolio Work, Quality / Stability / Reliability, Security & Compliance, Incidents & Support, Future Sustainability, Associate Wellness & Development.
scripts/update.sh <KEY> <field=value> [field=value ...]
| Field | Example |
|---|---|
| status | status=Closed |
| sp | sp=3 |
| priority | priority=Major |
| activity | activity=Product / Portfolio Work |
| component | component=Global Hub |
| parent | parent=ACM-30822 |
| sprint | sprint=current |
| assignee | assignee=-1 (-1 = current user) |
| link | link=https://github.com/.../pull/42 |
All fields run in parallel. Custom field IDs resolved dynamically.
Activity Type values: Associate Wellness & Development, Future Sustainability, Incidents & Support, Quality / Stability / Reliability, Security & Compliance, Product / Portfolio Work
scripts/link.sh <KEY> <URL_OR_ISSUE_KEY> [custom_title]
Auto-detects URL type for title: GitHub PR -> PR #N - repo, GitLab MR -> MR !N - repo, Google Drive -> Google Drive, Blog -> Blog: slug. If target is an issue key, sets it as parent instead.
The jira-ops CLI is bundled at scripts/jira-ops. Use it for any operation not covered by the high-level scripts above.
# Issue operations
scripts/jira-ops issue get <key> [fields]
scripts/jira-ops issue search <jql> [fields] [max]
scripts/jira-ops issue create <json-payload>
scripts/jira-ops issue update <key> <json-payload>
scripts/jira-ops issue delete <key>
scripts/jira-ops issue get-field <key> <field-name>
scripts/jira-ops issue set-field <key> <field-name> <val>
scripts/jira-ops issue transition <key> <status>
scripts/jira-ops issue transitions <key>
scripts/jira-ops issue link <type> <from> <to>
scripts/jira-ops issue comment <key> <text>
scripts/jira-ops issue comment-delete <key> <comment-id>
scripts/jira-ops issue remote-link <key> <url> <title>
# Sprint / Board
scripts/jira-ops board list <project> [max]
scripts/jira-ops sprint list <board-id>
scripts/jira-ops sprint issues <sprint-id> [fields] [max]
scripts/jira-ops sprint move <sprint-id> <keys...>
# Custom field mapping
scripts/jira-ops field discover
scripts/jira-ops field search <pattern>
scripts/jira-ops field get <name>
# Global flag: --json outputs raw JSON
scripts/jira-ops --json issue get ACM-123
Source scripts/jira-ops.sh to use library functions directly. See references/api-reference.md for the full function reference (CRUD, search, transitions, ADF builders, sprint operations, URL title detection).
source "${CLAUDE_SKILL_DIR}/scripts/jira-ops.sh"
jira_search 'project = ACM AND status = Open'
ISSUE_KEY=$(jira_create_issue "$payload") || exit 1
jira_transition "$ISSUE_KEY" "In Progress"
| Variable | Required | Description |
|---|---|---|
JIRA_USER | Yes | Atlassian account email |
JIRA_API_TOKEN | Yes | API token (not password) |
JIRA_BASE_URL | Yes | e.g. https://your-domain.atlassian.net |
JIRA_AUTH_TYPE | No | basic-header (default), basic, bearer |
basic-header works through corporate proxiesadf_* builder functions in library modeparent field, not legacy custom fieldsjira-ops sprint move or jira_move_to_sprint/rest/api/3/search/jql (GET), not the deprecated POST endpointjira-ops field discover once, then use jira-ops field get "Story Points" to look up IDs