メニュー
Tools for interaction with jira production cloud environment. Use when asked to: search or filter issues with JQL, create or update tickets, transition issue status, manage epics and sprints, log work, add comments, or generate project reports. Trigger keywords: jira.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | jira |
| description | Tools for interaction with jira production cloud environment. Use when asked to: search or filter issues with JQL, create or update tickets, transition issue status, manage epics and sprints, log work, add comments, or generate project reports. Trigger keywords: jira. |
| compatibility | Requires jira agent (jira.agent.md) and jira MCP server. |
Delegate ALL operations to the jira agent. The agent provisions the Jira MCP server
and has the required tools for all read and write operations.
Access Jira Cloud to read and manage issues, epics, sprints, boards, projects, and worklogs. Use for any task involving Jira tickets, sprint planning, status updates, linking issues, or reporting.
Include jira in your prompt to activate this skill.
When connected to the Jira MCP server the agent MUST enforce:
PD when the user does not specify a project — never override an explicit project key"https://${JIRA_ORG}.atlassian.net" — do NOT call getAccessibleAtlassianResourcesmaxResults: 10 / limit: 10; paginate with startAt when a task requires more resultsBefore taking any action the agent MUST:
jira_get_all_projects with maxResults=1 as a lightweight connectivity probe.jira Find all open bugs assigned to me in project PD
jira Show all issues in the current active sprint
jira Create a bug in project PD: "Login fails on Safari" assigned to john@example.com
jira Move PD-123 to In Progress
jira Add comment to PD-456: "Fixed in PR #89, pending review"
jira Show all stories linked to epic PD-10
jira Log 2h 30m on PD-789 with comment "Implemented feature"
Common JQL patterns (replace PD with the target project key as needed):
assignee = currentUser() AND status != Doneproject = PD AND issuetype = Bug AND priority = Highsprint in openSprints() AND status = "In Progress"updated >= -7d AND project = PDparent = PD-123 (child issues under an epic — field availability varies by instance; use jira_search_fields to verify)mcp-config.json, ~/.augment/mcp-config.json, etc.)jira.agent.md custom agent which owns the MCP server config.JIRA_TOKEN env var defined in .augment/.env.jira_search_fields to discover them before useCountly production environment specialist for product analytics, event tracking, and crash reporting. Use when asked to: validate event instrumentation, analyze user sessions, check retention metrics, investigate crash reports, or debug analytics flows in the production environment. Trigger keywords: countly-prd. Do NOT use for production analytics — use countly-prd instead.
Countly test environment specialist for product analytics, event tracking, and crash reporting. Use when asked to: validate event instrumentation, analyze test user sessions, check retention metrics, investigate crash reports, or debug analytics flows in the test/staging environment. Trigger keywords: countly-tst. Do NOT use for production analytics — use countly-prd instead.
Documentation search specialist for retrieving accurate, structured information from official docs, GitHub repositories, and private resources. Use when asked to: look up API references, find library usage examples, read official guides, search framework documentation, or retrieve content from a specific docs URL. Trigger keywords: doc-search. Do NOT use for real-time or frequently changing information — use web-search instead.
Grafana production environment specialist for metrics, logs, traces, dashboards, and alerting. Use when asked to: query Prometheus metrics, search Loki logs, analyze Tempo traces, manage dashboards, configure alert rules, or investigate issues in the production environment. Trigger keywords: grafana-prd. Do NOT use for test environment (use grafana-tst instead).
Grafana test environment specialist for metrics, logs, traces, dashboards, and alerting. Use when asked to: query Prometheus metrics, search Loki logs, analyze Tempo traces, manage dashboards, configure alert rules, or investigate issues in the test environment. Trigger keywords: grafana-tst. Do NOT use for production environment (use grafana-prd instead).
Graylog test environment specialist for log search, aggregation, and analysis. Use when asked to: search logs, find errors, query streams, analyze log patterns, investigate test run failures, debug issues, or check log volumes in the production environment. Trigger keywords: graylog-prd. Do NOT use for testing environment logs (use graylog-tst instead).