菜单
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 职业分类
Teach the user a new skill or concept within this workspace. Use when the user asks to learn, be taught, or build understanding over multiple sessions.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Produce a guided walkthrough of a code diff, pull request, merge request, commit range, or staged changes. Use when the user asks to explain, narrate, summarize, review, or walk through a diff. Supports configurable depth and output formats, defaults to HTML, and uses Plannotator when available.
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.
React-oriented UI/UX design principles for frontend development. Covers React patterns, component architecture, hooks, layout, typography, color, accessibility, and responsive design. Use when building React UI, reviewing frontend code, designing components, or making visual/interaction decisions. Assumes React with a meta-framework (TanStack Start, Next.js, Remix, etc.).
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
| 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