菜单
Create, update, transition, and manage Jira tickets. Use when working with Jira issues, tracking work, or automating ticket workflows.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create effective skills for OpenCode agents. Load FIRST before writing any SKILL.md. Provides required format, naming conventions, progressive disclosure patterns, and validation. Use when building, reviewing, or debugging skills.
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task.
Generate hierarchical AGENTS.md knowledge base for a codebase. Creates root + complexity-scored subdirectory documentation.
Multi-repository codebase exploration. Research library internals, find code patterns, understand architecture, compare implementations across GitHub/npm/PyPI/crates. Use when needing deep understanding of how libraries work, finding implementations across open source, or exploring remote repository structure.
Dialogue-driven spec development through skeptical questioning and iterative refinement. Triggers: "spec this out", feature planning, architecture decisions, "is this worth it?" questions, RFC/design doc creation, work scoping. Invoke Librarian for unfamiliar tech/frameworks/APIs.
Detect whether the current project uses jj (Jujutsu) or git for version control. Run this BEFORE any VCS command to use the correct tool.
| name | jira-tool |
| description | Create, update, transition, and manage Jira tickets. Use when working with Jira issues, tracking work, or automating ticket workflows. |
CLI for Jira operations via Cloudflare Access authentication.
| Task | Command |
|---|---|
| Create ticket | scripts/jira-tool.sh create -p PROJECT -s "Summary" [-t Type] [-d "Desc"] [-l labels] |
| Get ticket | scripts/jira-tool.sh get ISSUE-KEY |
| Update ticket | scripts/jira-tool.sh update ISSUE-KEY [-s "Summary"] [-d "Desc"] [-a user] |
| Add comment | scripts/jira-tool.sh comment ISSUE-KEY "Comment body" |
| Transition | scripts/jira-tool.sh transition ISSUE-KEY [STATUS] |
| Close ticket | scripts/jira-tool.sh close ISSUE-KEY |
| Assign | scripts/jira-tool.sh assign ISSUE-KEY [username] |
| Search | scripts/jira-tool.sh search "JQL query" [max] |
| Auth status | scripts/jira-tool.sh status |
Auth is automatic via cloudflared. On first use or token expiry:
Check status: scripts/jira-tool.sh status
scripts/jira-tool.sh create \
-p PROJECT \
-s "Fix authentication bug" \
-t Bug \
-d "Detailed description" \
-l "urgent,backend" \
--priority High \
-a username
Required: -p (project), -s (summary)
Optional: -t (type, default: Task), -d (description), -l (labels), --priority, -a (assignee), --parent (for Sub-task), --epic (link to epic)
# Create a sub-task under an existing issue
scripts/jira-tool.sh create -p PROJ -s "Subtask summary" -t Sub-task --parent PROJ-123
# Create task linked to an epic
scripts/jira-tool.sh create -p PROJ -s "Task summary" --epic PROJ-100
Note: Assignee uses Jira username (not email). Find via search on existing tickets.
scripts/jira-tool.sh get PROJ-123
Returns JSON with summary, status, assignee, priority, description, labels.
scripts/jira-tool.sh update PROJ-123 -s "New summary" -d "New desc" -a newuser
scripts/jira-tool.sh comment PROJ-123 "Fixed in commit abc123"
List available transitions:
scripts/jira-tool.sh transition PROJ-123
Transition to status:
scripts/jira-tool.sh transition PROJ-123 "In Progress"
Tries common close statuses (Done, Closed, Resolved, Complete):
scripts/jira-tool.sh close PROJ-123
scripts/jira-tool.sh assign PROJ-123 username # assign
scripts/jira-tool.sh assign PROJ-123 -1 # unassign
scripts/jira-tool.sh search "project = DEVTOOLS AND status = Open" 50
scripts/jira-tool.sh delete PROJ-123
| Query | JQL |
|---|---|
| My open tickets | assignee = currentUser() AND status != Done |
| Project backlog | project = PROJ AND status = "To Do" |
| Recently updated | project = PROJ AND updated >= -7d |
| High priority | priority in (High, Highest) AND status != Done |
Most commands return JSON. Parse with jq:
scripts/jira-tool.sh get PROJ-123 | jq '.fields.status.name'
scripts/jira-tool.sh search "assignee = currentUser()" | jq '.issues[].key'
# Create and start work
scripts/jira-tool.sh create -p PROJ -s "Implement feature X" -t Task
scripts/jira-tool.sh transition PROJ-456 "In Progress"
# Update progress
scripts/jira-tool.sh comment PROJ-456 "Initial implementation done"
# Complete
scripts/jira-tool.sh close PROJ-456