Menu
Interactive CLI for Atlassian Jira issue, epic, and sprint management.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Headless browser automation CLI optimized for AI agents. Uses snapshot + refs system for 93% less context overhead vs Playwright. Purpose-built for web testing, form automation, screenshots, and data extraction.
Manage a gitflow branching workflow — starting and finishing feature, release, and hotfix branches; cutting versioned releases with changelog generation; coordinating emergency hotfixes directly to production; and keeping long-lived branches in sync. Activates when users mention gitflow, feature/release/hotfix branches, cutting a release, branching strategy, promoting an integration branch to production, tagging a version, or rolling back a live release. Also reaches for it when the user says "ship it", "promote dev to main", or "we need to hotfix prod" without naming gitflow. Skip for general git mechanics (commit messages, merge conflicts, interactive rebase, git education) or CI-failure debugging unrelated to a release.
Fixes a bug through test-driven debugging — reproduces it with a failing test, locates the root cause with evidence (file:line), then applies the smallest fix that resolves it without refactoring unrelated code. Use when the user wants to fix a bug, debug an issue, resolve an error, or investigate a failing test. Not for building new functionality (use implement-feature) or restructuring working code with no bug involved (use refactor).
Implements a new feature end-to-end as a senior staff engineer would — discovers project conventions, researches current best practices, drafts a plan for approval, then builds it with parallel subagents that reuse existing code, skip speculative abstractions, and verify with tests before completion. Use when the user wants to implement, build, add, or ship new functionality (a feature, endpoint, component, module, or integration) — not for fixing an existing bug (use fix-bug) or restructuring code that already works (use refactor).
Restructures existing code without changing its behavior — maps callers and test coverage, adds characterization tests where coverage is thin, then applies the change in small steps verified against the full test suite after each one. Use when the user wants to refactor, extract a method or class, simplify logic, reduce duplication, improve naming, restructure modules, or pay down technical debt in code that already works. Not for adding new functionality (use implement-feature) or fixing broken behavior (use fix-bug).
Runs a comprehensive multi-agent code review of a PR, commit, or the whole codebase across six dimensions (correctness, performance, code style, test coverage, error handling, and simplicity/over-engineering) and returns a severity-ranked report with file:line findings and fix suggestions. Use when the user wants a thorough code review, asks to review a PR or diff, or wants over-engineered code flagged for simplification. Analysis only, identifying issues without modifying code, committing, or running tests. Not for a security-focused audit (use review-security) or a visual/UX design critique (use review-design).
| name | jira-cli |
| description | Interactive CLI for Atlassian Jira issue, epic, and sprint management. |
| disable-model-invocation | true |
Interactive command-line tool for Atlassian Jira that minimizes reliance on the web interface while maintaining essential functionality for daily Jira operations.
JiraCLI (jira-cli) is a command line tool for managing Jira issues, epics, and sprints. Supports both Jira Cloud and on-premise installations with multiple authentication methods.
For AI use, always add --plain flag to get plain text output suitable for parsing.
Use this skill when:
# List recent issues (always use --plain for AI)
jira issue list --plain
# View issue details
jira issue view ISSUE-1 --plain
# Create an issue
jira issue create -tBug -s"Bug title" -yHigh -b"Description"
# Assign issue to yourself
jira issue assign ISSUE-1 $(jira me)
# Move issue to "In Progress"
jira issue move ISSUE-1 "In Progress"
# Add comment
jira issue comment add ISSUE-1 --comment "My comment"
# Add worklog
jira issue worklog add ISSUE-1 "2h" --comment "Implementation work"
For detailed command reference and examples, load the appropriate reference file:
Load: references/commands.md
Use this file when you need:
Load: references/workflows.md
Use this file when you need:
Load: references/scripting.md
Use this file when you need:
# Combine flags for precise queries (always add --plain)
jira issue list --plain -a$(jira me) -yHigh -s"To Do" --created -7d -lbackend
# Use tilde (~) as NOT operator
jira issue list --plain -s~Done --created-before -24w
# Filter by multiple criteria
jira issue list --plain -yHigh,Critical -s"In Progress" -lbug
# List issues I'm watching
jira issue list --plain -w
# List issues assigned to no one created this week
jira issue list --plain -ax --created week
# List issues created within an hour
jira issue list --plain --created -1h
# List issues from history (recently viewed)
jira issue list --plain --history
# List current active sprint issues
jira sprint list --plain --current
# List current sprint issues assigned to me
jira sprint list --plain --current -a$(jira me)
# List previous sprint issues
jira sprint list --plain --prev
# List next planned sprint issues
jira sprint list --plain --next
# List future and active sprints
jira sprint list --plain --state future,active
# List issues in a specific sprint (use sprint ID)
jira sprint list --plain SPRINT_ID
# Add issues to a sprint
jira sprint add SPRINT_ID ISSUE-1 ISSUE-2
# List epics in table view
jira epic list --plain --table
# List issues in an epic
jira epic list --plain KEY-1
# List unassigned high priority issues in an epic
jira epic list --plain KEY-1 -ax -yHigh
# Add issues to an epic (up to 50 at once)
jira epic add EPIC-KEY ISSUE-1 ISSUE-2
# Remove issues from an epic
jira epic remove ISSUE-1 ISSUE-2
# Get ticket count per sprint
sprints=$(jira sprint list --table --plain --columns id,name --no-headers)
echo "${sprints}" | while read -r id name; do
count=$(jira sprint list "${id}" --plain --no-headers 2>/dev/null | wc -l)
printf "%s: %d\n" "${name}" "${count}"
done
# List tickets created today
jira issue list --plain --created -1d
# List high priority bugs assigned to me
jira issue list --plain -a$(jira me) -tBug -yHigh
# Get issues by date range
jira issue list --plain --created week
jira issue list --plain --created month
jira issue list --plain --created -7d
jira issue list --plain --updated -30m