メニュー
This skill should be used when the user asks to "get Jira issue", "create Jira ticket", "search Jira", "update issue status", or needs to interact with Jira Data Center/Server instances.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Produce single-file, self-contained HTML artifacts instead of Markdown for any output a human will actually read. Use whenever the user asks for a "report", "research summary", "write-up", "spec", "plan", "PR explainer", "code review", "design mockup", "prototype", "dashboard", "deck", or anything that benefits from tables, SVG diagrams, color coding, side-by-side comparisons, sliders, drag-and-drop, or shareable visuals. Also use when the user wants to share something visual with a teammate, when a Markdown plan would exceed ~100 lines, when interactive tweaking would help (sliders, copy-as-JSON, copy-as-prompt buttons), or when the model is about to resort to ASCII-art charts or Unicode color blocks in Markdown. Strongly prefer this skill for any "summarize and present" task — even if the user doesn't explicitly say "HTML".
Use this skill whenever the user asks to look at GitHub PR feedback, PR review comments, review bot output, Gemini/Claude review feedback, or pasted reviewer suggestions and wants a markdown table that separates what should be fixed from what does not need to be fixed. This skill should trigger for PR feedback triage, deciding whether review comments are actionable, and producing a concise markdown report with yes/no emoji decisions and reasoning.
Use this skill whenever the user wants to interact with Google Cloud's Agent Registry using gcloud commands. Triggers on any mention of "agent registry", "agent-registry", "mcp-servers", "gcloud agents", "register an agent", "list agents", "create a service", "agent service", or any request to manage agents, MCP servers, endpoints, or services in Google Cloud Agent Registry. Also triggers on requests to integrate or use the Google Agent Development Kit (ADK) with the Agent Registry.
Follow Kent Beck's "Tidy First" approach by strictly separating structural changes (renames, extractions, reorganizations that must not change behavior) from behavioral changes (features, bug fixes, logic changes). Use when refactoring, restructuring code, renaming variables/functions, extracting methods, separating concerns, preparing code for new features, or whenever you need structural and behavioral changes to land in separate commits.
Read this skill before making git commits
Automates the end-to-end Git workflow: branch creation, staging, committing, pushing, and opening or updating a GitHub pull request. Use when a feature or fix is ready for review and requires a structured PR, or when branch changes may need to be pushed to an existing PR for follow-up review.
| name | jira-datacenter |
| description | This skill should be used when the user asks to "get Jira issue", "create Jira ticket", "search Jira", "update issue status", or needs to interact with Jira Data Center/Server instances. |
| version | 0.1.0 |
Interact with Jira Data Center/Server instances via REST API.
| Command | Description |
|---|---|
| get | Get issue details by key |
| search | Search issues using JQL |
| create | Create a new issue |
| update | Update issue fields |
| transition | Change issue status |
| comment | Add a comment to an issue |
| assign | Assign issue to a user |
| projects | List available projects |
| transitions | List available transitions for an issue |
Environment variables (can be in .env file):
JIRA_BASE_URL - Your Jira instance URL (e.g., https://jira.company.com)JIRA_PAT - Personal Access Token (preferred)OR for basic auth:
JIRA_BASE_URL - Your Jira instance URLJIRA_USERNAME - Your usernameJIRA_PASSWORD - Your passwordJIRA_PATuvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py COMMAND [OPTIONS]
uvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py get PROJ-123
Options:
--fields FIELD1,FIELD2 - Specific fields to return (default: all)--comments - Include comments--json - Output as JSONuvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py search "project = PROJ AND status = Open"
Options:
--max N - Maximum results (default: 50)--fields FIELD1,FIELD2 - Fields to include--json - Output as JSONuvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py create \
--project PROJ \
--type Bug \
--summary "Issue title" \
--description "Detailed description"
Options:
--project KEY - Project key (required)--type TYPE - Issue type: Bug, Task, Story, Epic, etc. (required)--summary TEXT - Issue summary/title (required)--description TEXT - Issue description--priority NAME - Priority: Highest, High, Medium, Low, Lowest--assignee USERNAME - Assign to user--labels LABEL1,LABEL2 - Comma-separated labels--components COMP1,COMP2 - Comma-separated component namesuvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py update PROJ-123 \
--summary "New title" \
--description "Updated description"
Options:
--summary TEXT - New summary--description TEXT - New description--priority NAME - New priority--labels LABEL1,LABEL2 - Replace labels--add-labels LABEL - Add labels--remove-labels LABEL - Remove labels# List available transitions
uvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py transitions PROJ-123
# Transition to new status
uvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py transition PROJ-123 "In Progress"
uvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py comment PROJ-123 "This is my comment"
uvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py assign PROJ-123 username
Use - to unassign:
uvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py assign PROJ-123 -
uvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py projects
# Get issue with comments
uvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py get PROJ-123 --comments
# Search for my open issues
uvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py search "assignee = currentUser() AND status != Done"
# Create a bug with priority
uvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py create \
--project PROJ \
--type Bug \
--summary "Login fails with special characters" \
--description "Steps to reproduce:\n1. Enter username with @\n2. Click login\n3. Error appears" \
--priority High \
--labels security,login
# Move issue to In Progress
uvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py transition PROJ-123 "In Progress"
# Add a comment
uvx --with requests --with python-dotenv --with typer --with rich \
python ~/.claude/skills/jira-datacenter/scripts/jira.py comment PROJ-123 "Fixed in commit abc123"
--json flag for machine-readable JSON outputThis skill uses Jira REST API v2 (/rest/api/2/), which is compatible with: