Jira CLI

Manage Jira tickets offline via local Markdown and YAML.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/mikesmullin/jira --skill jira-cli-mikesmullin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Jira CLI
Source: https://github.com/mikesmullin/jira/tree/main
Command: npx skills add https://github.com/mikesmullin/jira --skill jira-cli-mikesmullin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires js-yaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines Jira ticket management by enabling offline work, reducing the need for constant internet connectivity and simplifying complex operations.

Core Features & Use Cases

  • Offline-First Workflow: Pull tickets locally, work offline, and sync changes later.
  • Batch Ticket Creation: Define and create multiple tickets from a single YAML file.
  • Plan/Apply Workflow: Preview changes before applying them to Jira, similar to Terraform.
  • Use Case: A developer can pull their assigned tickets, make edits and add comments while on a flight, then plan their changes to see a diff and apply them once back online.

Quick Start

Use the Jira CLI skill to pull all your assigned tickets from Jira.

Frequently Asked Questions about Jira CLI

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Jira tickets offline and sync changes later?

To manage Jira tickets offline, you can pull tickets to local Markdown storage for editing without internet connectivity. Once back online, a plan/apply workflow previews your changes before syncing them to Jira via the REST API.

Can I create multiple Jira tickets at once from a YAML file?

Yes, you can batch create multiple Jira tickets by defining them in a single YAML file. The CLI processes this YAML file to generate multiple tickets simultaneously through the Jira REST API.

What is a plan/apply workflow for Jira ticket management?

A plan/apply workflow for Jira ticket management previews pending local changes as a diff before committing them. You review the diff generated from local Markdown edits, then apply the changes to sync with the Jira REST API.

Does the Jira CLI support full CRUD operations through the REST API?

Yes, the Jira CLI supports full CRUD operations on tickets by integrating directly with the Jira REST API. You can retrieve, create, update, and delete tickets while maintaining an offline-first workflow using local Markdown files.

Do I need any specific dependencies to run the Jira CLI for offline ticket management?

You need the js-yaml dependency installed to run the Jira CLI. This library parses the YAML files required for batch ticket creation and the offline-first Markdown storage workflow.

What is the best way to edit Jira tickets locally without an internet connection?

The best way to edit Jira tickets without an internet connection is using an offline-first CLI that stores tickets in local Markdown files. You pull assigned tickets, edit them offline, and sync changes via a plan and apply process later.