acli
Atlassian CLI (acli)
acli is Atlassian's official command-line tool for Jira Cloud, Confluence Cloud, and org admin operations. It replaces terminal-based Jira automation that previously required raw REST calls, and unifies Jira + Confluence + admin actions behind one binary with one credential store per product.
This skill teaches how to drive acli for any intent: one-off commands, batch mutations, scripted pipelines, and CI jobs. Repo-specific integration (how this skill plugs into the host repo's workflow, TMS modality, project conventions, anti-patterns) lives in the companion file <repo-core>/references/acli-integration.md — load it on demand. See "Navigation" below.
Why this skill exists
acli has several traits that make it easy to misuse:
- Silent pagination truncation.
workitem searchwithout--paginatereturns the first page only — no warning. Scripts that count or iterate keys read the wrong number of items. - Auth is per-product.
acli jira auth logindoes not authenticateacli admin,acli confluence, oracli rovodev. There is also a top-levelacli authfor global OAuth (newer surface). Each scope has its own session. - The "work item" vs "issue" split. The CLI renamed commands (
jira issue→jira workitem) but the JSON response still has a top-levelissues[]array and CSV inputs still useissueType/parentIssueIdspellings. Mixing old and new terminology in the same script works, but confuses readers. - Unknown subcommands fail silently. Typing
acli jira workflow --helpdoes NOT error — it falls back toacli jira --helpwith exit 0. So "no error" ≠ "command exists". Always verify by checking the help body actually changed. - Hard limits the docs do not advertise.
aclicannot list custom fields, edit custom-field values on existing items, manage workflows, manage issue types, or touch project versions/components. Seereferences/gotchas.md.
The body below covers the core that applies to almost every session. The references/ directory holds the deep material — load only the one you need.