jira
This skill provides workflows for managing Jira tickets using Atlassian's official CLI (acli). It should be used when creating, viewing, searching, or managing Jira work items from the command line. Triggers on "create jira ticket", "search jira", "view issue", "jira cli", "jira workitem".
What this skill does
# ACLI - Atlassian CLI for Jira This skill enables efficient Jira ticket management using Atlassian's official `acli` command-line tool. ## Prerequisites Verify acli is installed and authenticated: ```bash which acli && acli jira auth status ``` ## Core Commands ### Create Tickets **Basic:** ```bash acli jira workitem create \ --project "<PROJECT_KEY>" \ --type "<Task|Bug|Story|Epic>" \ --summary "<title>" ``` **With details:** ```bash acli jira workitem create \ --project "<PROJECT_KEY>" \ --type "<type>" \ --summary "<title>" \ --description "<description>" \ --assignee "<email|@me|default>" \ --label "<label1,label2>" \ --parent "<PARENT-KEY>" # Optional: for sub-tasks ``` **Interactive (opens editor):** ```bash acli jira workitem create --project "<PROJECT_KEY>" --type "<type>" --editor ``` **From file (first line = summary, rest = description):** ```bash acli jira workitem create --from-file "<path>" --project "<PROJECT_KEY>" --type "<type>" ``` **From JSON (for rich formatting + custom fields):** ```bash acli jira workitem create --from-json "<path.json>" ``` ### View Tickets ```bash acli jira workitem view <KEY-123> # Basic acli jira workitem view <KEY-123> --json # JSON output acli jira workitem view <KEY-123> --fields "*all" # All fields acli jira workitem view <KEY-123> --web # Open browser ``` ### Search Tickets (JQL) ```bash acli jira workitem search --jql "<query>" --limit 20 acli jira workitem search --jql "<query>" --paginate # All results acli jira workitem search --jql "<query>" --json # JSON output acli jira workitem search --jql "<query>" --csv # CSV output acli jira workitem search --jql "<query>" --count # Count only ``` **Common JQL patterns:** - `project = PRE` - By project - `assignee = currentUser()` - My tickets - `status = "In Progress"` - By status - `labels = urgent` - By label - `created >= -7d` - Recent tickets - `project = PRE AND status != Done ORDER BY priority DESC` - Combined ### Edit Tickets ```bash acli jira workitem edit --key <KEY-123> --summary "<new title>" acli jira workitem edit --key <KEY-123> --description "<new desc>" acli jira workitem edit --key "<KEY-1,KEY-2>" --label "<labels>" # Bulk ``` ### Transitions ```bash acli jira workitem transition --key <KEY-123> --status "In Progress" acli jira workitem transition --key <KEY-123> --status "Done" acli jira workitem transition --jql "<query>" --status "<status>" # Bulk ``` ### Assignments ```bash acli jira workitem assign --key <KEY-123> --assignee "<email>" acli jira workitem assign --key <KEY-123> --assignee "@me" acli jira workitem assign --key <KEY-123> --assignee "default" ``` ### Comments ```bash acli jira workitem comment create --key <KEY-123> --body "<text>" acli jira workitem comment list --key <KEY-123> acli jira workitem comment update --key <KEY-123> --comment-id <id> --body "<text>" acli jira workitem comment delete --key <KEY-123> --comment-id <id> ``` ### Other Operations ```bash acli jira workitem clone --key <KEY-123> acli jira workitem link create --key <KEY-123> --link-key <KEY-456> --type "blocks" acli jira workitem archive --key <KEY-123> acli jira workitem delete --key <KEY-123> ``` ### Projects ```bash acli jira project list --limit 50 acli jira project view <PROJECT_KEY> ``` ## JSON Template for Rich Tickets For tickets requiring rich formatting (headings, lists, code blocks), use ADF (Atlassian Document Format). Reference `references/adf-template.json` for the full structure. **Generate a template:** ```bash acli jira workitem create --generate-json > ticket-template.json ``` ## Workflow Patterns ### Create well-structured bug report 1. Gather: summary, steps to reproduce, expected vs actual behavior 2. Use `--editor` or `--from-json` for rich formatting 3. Add labels: `bug`, severity, component ### Bulk operations 1. First search with `--jql` to verify scope 2. Use comma-separated keys or `--jql` flag on edit/transition commands ### Quick ticket from terminal ```bash acli jira workitem create -p PRE -t Task -s "Quick task" -a @me ```
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.