메뉴
Use when working with JIRA from the terminal. Use when asked to look up, create, update, transition, assign, or comment on JIRA issues. Use for sprint or epic operations.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use this skill whenever the user wants to commit changes, stage files, write a commit message, or run git commit — even if they just say "commit this", "save my changes", or "make a commit". Guides writing well-structured commit messages following the Conventional Commits specification, enforcing scope rules from .conform.yaml, protecting main/master branches, and ensuring clean staging hygiene before every commit.
Use when working with flake-parts or dev-flake — structuring flakes, defining perSystem outputs, writing reusable flake modules, using withSystem or moduleWithSystem, exporting flakeModules, setting up dev environments with dev-flake, or debugging flake-parts evaluation.
Use when you need to read, explore, or reference source code from any Git repository. Use before cloning manually or asking the user for a path.
Use when writing, editing, or reviewing Nix code — including NixOS modules, Home Manager configuration, packages, and overlays. Covers Nix coding style, module system patterns, common lib functions, and tooling (nixfmt, deadnix, statix). For flake-parts-specific patterns use the flake-parts skill instead.
| name | jira-cli-operations |
| description | Use when working with JIRA from the terminal. Use when asked to look up, create, update, transition, assign, or comment on JIRA issues. Use for sprint or epic operations. |
jira CLI (ankitpokhrel/jira-cli) wraps JIRA REST API. Config at ~/.config/.jira/.config.yml. Default project from config, override with -p PROJECT.
| Task | Command |
|---|---|
| List issues | jira issue list [--status "In Progress"] [-a email] [-t Bug] [-l label] [--created month] |
| View issue | jira issue view ISSUE-123 [--comments 3] [--raw] [--plain] |
| Create issue | jira issue create -t Task -s "Summary" [-b "Description"] [-a email] [-y High] [-l bug] [--no-input] |
| Edit issue | jira issue edit ISSUE-123 -s "New summary" [--no-input] |
| Transition | jira issue move ISSUE-123 "In Progress" [--comment "starting work"] |
| Assign | jira issue assign ISSUE-123 user@example.com |
| Assign to self | jira issue assign ISSUE-123 $(jira me) |
| Unassign | jira issue assign ISSUE-123 x |
| Comment | jira issue comment add ISSUE-123 "Message here" |
| Log work | jira issue worklog add ISSUE-123 "2h 30m" [--comment "desc"] [--no-input] |
| Link issues | jira issue link ISSUE-123 ISSUE-456 "Blocks" |
| Delete issue | jira issue delete ISSUE-123 [--cascade] |
| Open in browser | jira open ISSUE-123 |
| List sprints | jira sprint list [--table] [--state active,closed] [--plain] |
| Current sprint issues | jira sprint list --current [--plain --columns key,summary,status] |
| Add to sprint | jira sprint add SPRINT-ID ISSUE-123 |
| List epics | jira epic list |
| Add to epic | jira epic add EPIC-123 ISSUE-456 |
Use --no-input to skip prompts, --raw for JSON output:
jira issue create -t Bug -s "Fix login crash" -y Critical --no-input
jira issue list --raw | jaq '.[].key'
echo "Detailed description here" | jira issue create -t Task -s "Summary"
jira issue create -t Story -s "Feature" --template /path/to/template.md
Prefix with minus:
jira issue edit ISSUE-123 --label -deprecated --component -BE
jira issue list --plain --columns key,summary,status,assignee
jira issue list --plain --no-headers --delimiter "|"
jira issue create -t Story -s "Task" --custom story-points=5
jira issue list -q "project = PROJ AND status != Closed ORDER BY priority DESC"
jira issue list --created month -s "In Progress" -a $(jira me)
KEY=$(jira issue create -t Task -s "Summary" --no-input --raw | jaq -r '.key')
jira issue move "$KEY" "In Progress"
# Find your open work
jira issue list -a $(jira me) -s "In Progress" --plain --columns key,summary,status
# Move forward
jira issue move ISSUE-123 "Code Review" --comment "Ready, please review"
# Log time
jira issue worklog add ISSUE-123 "1h 30m" --comment "Implemented fix" --no-input
KEY=$(jira issue create -t Bug -s "Login fails on empty input" -y High -l bug --no-input --raw | jaq -r '.key')
jira issue assign "$KEY" dev@company.com
jira epic add EPIC-42 "$KEY"
jira sprint list --current --plain --columns key,summary,status,assignee
--no-input in scripts — command hangs waiting for input. Always add for automation.-s for status in list — -s is summary in create/edit, status in list. Context-dependent flag.view/edit/move — positional arg, required.--no-input — stdin goes to body, but prompts still block. Add --no-input.jira issue move ISSUE-123 "Done" might fail if workflow uses "Closed". Check board workflow or use jira issue view to see available transitions.--type on create — prompts interactively without --no-input and --type.