메뉴
Manage Jira issues via the jira-cli tool.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Record a durable engineering decision in the repo's append-only decision log (docs/decisions.md by default). Use after choosing between real alternatives — a dependency, a version pin, an architecture or protocol choice, a deliberate non-implementation, or a reversal of an earlier decision. Also use when the user says "log that decision", "write this down", or asks what was decided and why.
Structural code search and refactoring via ast-grep. Reach for this when Edit fails with "old_string not unique", when refactoring across formatting variations, or when matching code shape rather than text.
Outline a file or package (functions, classes, methods, types, imports, exports) instead of reading it whole. Use before opening an unfamiliar or large file to orient, when surveying a package's API surface, or to find where a symbol is defined so you can Read just that range -- any "what's in / list / show me the structure of" need. Not for "where is X used" (search) or "how does X work" (read the body).
How to author Claude Code plugins (agents, skills, commands, hooks, MCP servers) and distribute them via a marketplace. Use when creating, structuring, or revising a plugin, deciding which skill pattern fits, or writing SKILL.md / agent / hook / manifest files.
Implement TODO.md items via isolated subagents, then adversarially verify correctness. Drives a phased loop that implements one checkbox at a time, runs independent lint/test/review subagents, handles human verification, and commits per subsection.
Create and maintain structured TODO.md implementation plans with phased tasks, testing philosophy, and verification checklists. This skill should be used when the user asks to create a TODO file, implementation plan, project roadmap, or phased development plan. Also use when asked to update or extend an existing TODO.md in this style.
| name | jira-cli |
| description | Manage Jira issues via the jira-cli tool. |
Assume jira-cli is installed and configured.
Project flag: Always use -p PROJ to specify project explicitly (don't rely on defaults)
Ask the user to use the web UI for attachments/images and visual board operations -- these can't be done from the CLI.
jira issue view -p PROJ PROJ-123 # Read requirements
jira issue assign PROJ-123 $(jira me) # Assign to user
# ... implement ...
jira issue comment add PROJ-123 "Fixed in $(git rev-parse --short HEAD)"
jira issue move PROJ-123 "Done" # Close when complete
Extract only needed fields to minimize context usage:
# Get specific fields only
jira issue view -p PROJ PROJ-123 --raw | jq -r '.fields.status.name'
# List keys for iteration
jira issue list -p PROJ --plain --no-headers --columns KEY
See jira-cli reference guide for command syntax, JQL, filter flags, output formats, and data extraction patterns.