메뉴
Work with Jira over its REST API (no MCP) — read/search (JQL), look up tickets, my board/sprint, create/comment/@mention/transition/link/worklog, MR investigation, clone the ticket's repo. Use for any read/search/create/update/transition on Jira issues, or references to a remembered board, project, epic, or person.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Systematic performance profiling and optimization with a mandatory baseline-first gate — measure before changing, re-measure after. Use when something is slow or you need to hit a latency/throughput target.
Blameless post-mortem / RCA — gathers facts, reconstructs a timeline, runs 5-Whys, defines action items, writes the post-mortem file and commits it. Use after an incident or outage.
Structured design dialogue with a visual companion — produces an approved spec and design artifacts before any implementation begins. Use at the start of a feature, before writing code.
Thorough, research-grounded code review of a change, PR, or MR — multi-lens (correctness, security, simplification, tests), severity-ranked with impact + fix, configurable depth, optional PR comments. Use when asked to review code, "do a code review", "review this PR/MR", "review my changes/diff/branch", or audit a changeset before merge.
Use when the user asks to research, investigate, analyze, find out, explore, examine, audit, or evaluate something — structured multi-source research with consulting, library-doc search, web search, and guided output delivery.
Multi-agent code review AND remediation — dispatches correctness, security, and simplification reviewers in parallel, consolidates findings, then fixes criticals/highs. Use when reviewing a diff or PR before shipping.
| name | jira |
| description | Work with Jira over its REST API (no MCP) — read/search (JQL), look up tickets, my board/sprint, create/comment/@mention/transition/link/worklog, MR investigation, clone the ticket's repo. Use for any read/search/create/update/transition on Jira issues, or references to a remembered board, project, epic, or person. |
Read ../../references/codex-adapter.md, then read ../../../skills/jira/SKILL.md and follow the source skill through that Codex adapter. Keep the source skill's gates and rules.
Codex equivalents:
<plugin-root>/bin/jira for myself|get <KEY>|search "<JQL>"|transitions <KEY>|create '<fields-json>'|link <inward> "<Type>" <outward>|raw <METHOD> <path> [json]. It is throttle-aware/cached/self-pacing. Never use a bare PATH command, a versioned cache path, hand-written HTTP, module import, or ambient Jira MCP. For bulk work call the absolute CLI once per operation; stop on persistent 429 and increase pacing.JIRA_BASE_URL + a token (JIRA_API_TOKEN/JIRA_PAT/JIRA_PROD_PAT) from the environment. On missing config, use ../../../skills/jira/setup.md only as API guidance: explain how to provide variables to the current Codex environment or shell. Do not edit Claude settings, Codex global config, or secret files; never type/echo the secret.$magic first.<magician-state>/jira-memory.md; create it only after an authorized write.