jira-acli
v0.1.29acli-first Jira/Confluence toolkit: a pure-mechanics acli skill (bulk work-item ops via JQL, ADF↔markdown conversion) paired with jira-content (Bug/Story/Task/Epic/Sub-task + comments) and confluence-content (Spec/PRD pages), each owning its product's canonical templates, plus two preview-then-stop dispatchable agents (jira-expert, confluence-expert) that wrap them for multi-step work. Atlassian MCP is the fallback, not the default.
By KoBigLicense: MIT0 GitHub starsUpdated last month
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 3 skill or MCP entries
- Source updated
- Sep 5, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install jira-acli for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install jira-acli@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/wasikarn/jira-acliClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.
Plugin files
├── .claude-plugin/plugin.json├── skills/acli/SKILL.md├── skills/confluence-content/SKILL.md└── skills/jira-content/SKILL.md
Included Skills3
Mechanical driver for the acli CLI — a backend tool, not a content-authoring skill (same role as the Atlassian MCP): search, view, edit, transition, comment, link, clone, bulk ops via JQL, Confluence/admin ops, auth, and ADF↔markdown conversion. Use this skill directly only for mechanical/query/bulk/transition work with no template shape to get right.
Create or edit the content of a Confluence Spec/PRD page against the team's canonical template (business reason, scope, per-requirement GWT Acceptance Criteria) — via the Atlassian MCP (acli's `confluence page` command is view-only, it can't create or update). Use this BEFORE calling createConfluencePage/updateConfluencePage directly — never hand-build the page body.
Create or edit template-shaped Jira content — Bug/Story/Task/Epic/Sub-task descriptions and templated comments (status update/QA verification/blocker/decision record) — against the team's REQUIRED formats (GWT Acceptance Criteria, Thai PO/QA structure), whether acli or the Atlassian MCP does the write. Use BEFORE calling `acli jira workitem create/edit` or any Jira-create MCP tool — never hand-build template-shaped content.
Plugin manifests1
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "jira-acli",
"version": "0.1.29",
"description": "acli-first Jira/Confluence toolkit: a pure-mechanics acli skill (bulk work-item ops via JQL, ADF↔markdown conversion) paired with jira-content (Bug/Story/Task/Epic/Sub-task + comments) and confluence-content (Spec/PRD pages), each owning its product's canonical templates, plus two preview-then-stop dispatchable agents (jira-expert, confluence-expert) that wrap them for multi-step work. Atlassian MCP is the fallback, not the default.",
"author": {
"name": "KoBig",
"url": "https://github.com/wasikarn"
},
"license": "MIT",
"homepage": "https://github.com/wasikarn/jira-acli",
"repository": "https://github.com/wasikarn/jira-acli",
"defaultEnabled": false,
"keywords": [
"jira",
"confluence",
"atlassian",
"acli",
"adf"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[jira-acli on Agent Plugins Marketplace](https://pluginsmp.com/plugins/jira-acli)