メニュー
Jira issue tracking and incident management. Use when creating, searching, or updating Jira issues. Supports JQL queries for incident ticket analysis and alert fatigue tracking.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Pull incident context from alerting platforms (PagerDuty). Use when investigating who's on-call, incident history, alert patterns, or MTTR metrics.
Opsgenie alert management and on-call scheduling. Use for listing alerts, checking on-call, computing MTTA/MTTR, and alert fatigue analysis. Supports team and priority filtering.
Amplitude product analytics. Use when querying user events, funnels, retention, or product usage data. Provides event segmentation, user activity lookup, and annotation queries.
Google BigQuery data warehouse queries and schema inspection. Use when running SQL queries, listing datasets/tables, or inspecting table schemas in BigQuery.
MySQL/MariaDB database inspection and queries. Use when investigating table schemas, running queries, checking processlist, replication status, InnoDB engine status, or lock contention.
PostgreSQL database inspection and queries. Use when investigating table schemas, running queries, checking locks, replication status, or long-running queries.
| name | project-jira |
| description | Jira issue tracking and incident management. Use when creating, searching, or updating Jira issues. Supports JQL queries for incident ticket analysis and alert fatigue tracking. |
| allowed-tools | Bash(python *) |
IMPORTANT: Credentials are injected automatically by a proxy layer. Do NOT check for JIRA_API_TOKEN or JIRA_EMAIL in environment variables - they won't be visible to you. Just run the scripts directly; authentication is handled transparently.
Configuration environment variables you CAN check (non-secret):
JIRA_URL - Jira instance URL (e.g., https://your-company.atlassian.net)All scripts are in .claude/skills/project-jira/scripts/
Powerful search using Jira Query Language. Best for finding incident tickets, patterns, action items.
python .claude/skills/project-jira/scripts/search_issues.py --jql "JQL_QUERY" [--max-results N]
# Examples:
python .claude/skills/project-jira/scripts/search_issues.py --jql "type = Bug AND status != Done AND created >= -7d"
python .claude/skills/project-jira/scripts/search_issues.py --jql "labels = incident AND created >= -30d" --max-results 50
python .claude/skills/project-jira/scripts/get_issue.py --issue-key PROJ-123
python .claude/skills/project-jira/scripts/create_issue.py --project PROJ --summary "Title" --description "Details" [--type Bug] [--priority High] [--labels "incident,p1"]
python .claude/skills/project-jira/scripts/update_issue.py --issue-key PROJ-123 [--summary "New title"] [--status "In Progress"] [--priority High]
python .claude/skills/project-jira/scripts/add_comment.py --issue-key PROJ-123 --comment "Investigation findings..."
python .claude/skills/project-jira/scripts/list_issues.py --project PROJ [--max-results 20]
# Recent bugs
type = Bug AND created >= -7d ORDER BY created DESC
# Open incidents
type = Incident AND status != Done
# By label
labels IN ("incident", "p1", "alert-tuning")
# Text search
summary ~ "high CPU" OR description ~ "timeout"
# Stale issues
updated <= -90d AND status != Done
| Operator | Meaning | Example |
|---|---|---|
| = | Equals | status = Done |
| != | Not equals | status != Done |
| ~ | Contains text | summary ~ "error" |
| IN | In list | status IN ("Open", "In Progress") |
| >= | Greater/equal | created >= -7d |
| ORDER BY | Sort | ORDER BY created DESC |
1. Search for related incidents:
search_issues.py --jql "type = Incident AND created >= -30d"
2. Get details of specific incident:
get_issue.py --issue-key INC-456
3. Add investigation findings:
add_comment.py --issue-key INC-456 --comment "Root cause: ..."
4. Update status:
update_issue.py --issue-key INC-456 --status "Resolved"