Jira
- 17 installs
- 1 repo stars
- Updated April 27, 2026
- adrianhdezm/atlassian-bridge
jira is a Claude Code skill that interacts with Atlassian Jira via the atl CLI to read, create, update, delete and search issues, manage comments and browse projects.
About
jira is a Claude Code skill that wraps the community atl CLI to work with Atlassian Jira. A developer uses it to get, create, update, delete and search issues, manage comments and attachments, and browse projects from the agent. It verifies the CLI is installed and authenticated before running commands.
- Drives the community atl CLI to read, create, update, delete and search Jira issues
- Manages comments, attachments and projects with JQL search
- Requires @ai-foundry/atlassian-bridge and atl auth login
Jira by the numbers
- 17 all-time installs (skills.sh)
- Ranked #3,475 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Jul 7, 2026 (Skillselion catalog sync)
jira capabilities & compatibility
- Capabilities
- jira issues · jira search · jira comments · project management
- Works with
- jira · atlassian
- Use cases
- project management
- Pricing
- Free
What jira says it does
Interact with Atlassian Jira via the atl CLI — read, create, update, delete, and search issues, manage comments, and browse projects.
When creating issues, `--project` and `--type` are required. Common types: `Task`, `Bug`, `Story`, `Epic`, `Sub-task`.
npx skills add https://github.com/adrianhdezm/atlassian-bridge --skill jiraAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 17 |
|---|---|
| repo stars | ★ 1 |
| Last updated | April 27, 2026 |
| Repository | adrianhdezm/atlassian-bridge ↗ |
What it does
Create, read, update and search Jira issues, manage comments and attachments and browse projects via the atl CLI.
Who is it for?
Developers who want an agent to manage Jira issues and comments from the terminal.
Skip if: Users without the atl CLI installed or without an authenticated Atlassian account.
When should I use this skill?
When the user wants to get, create, search or comment on Jira issues or list projects.
What you get
Jira issues, comments and projects can be managed directly from agent commands.
By the numbers
- 8 issue actions
- 5 comment actions (list/get/add/update/delete)
- 2 project actions (get/list)
Files
Jira (atl CLI)
Prerequisites
Before running any Jira command, verify the CLI is available and authenticated:
1. Run atl --version. If it fails, stop and tell the user:
TheatlCLI is not installed. Install it withnpm i -g @ai-foundry/atlassian-bridgeand then runatl auth login.
>
Note:atlis NOT the official Atlassian CLI. It is a community project (@ai-foundry/atlassian-bridge).
2. Run atl auth status. If not authenticated, stop and tell the user:
You are not logged in. Run atl auth login to authenticate with your Atlassian account.Only proceed once both checks pass.
Available Commands
Issues
| Action | Command |
|---|---|
| Get | atl jira issues get <issueKey> |
| Create | atl jira issues create <summary> --project <key> --type <name> [--description <adf>] [--parent <key>] [--labels <csv>] |
| Update | atl jira issues update <issueKey> [--summary <text>] [--description <adf>] [--parent <key>] [--labels <csv>] [--status <name>] |
| Delete | atl jira issues delete <issueKey> |
| Search | atl jira issues search <jql> [--limit <n>] [--cursor <token>] [--fields <csv>] |
| Children | atl jira issues children <issueKey> |
| List Attachments | atl jira issues list-attachments <issueKey> |
| Get Attachment | atl jira issues get-attachment <attachmentId> |
Attachments
| Action | Command |
|---|---|
| List | atl jira attachments list <issueKey> |
| Get | atl jira attachments get <attachmentId> |
Comments
| Action | Command |
|---|---|
| List | atl jira comments list <issueKey> [--limit <n>] [--cursor <n>] |
| Get | atl jira comments get <commentId> --issue <issueKey> |
| Add | atl jira comments add <issueKey> --body <adf> |
| Update | atl jira comments update <commentId> --issue <issueKey> --body <adf> |
| Delete | atl jira comments delete <commentId> --issue <issueKey> |
Projects
| Action | Command |
|---|---|
| Get | atl jira projects get <keyOrId> |
| List | atl jira projects list [--limit <n>] [--cursor <token>] [--query <text>] |
Guidelines
- When the user mentions an issue, expect a key like
PROJ-123. Use it directly withatl jira issues get. - For search, build a valid JQL query from the user's intent (e.g.
project = PIXEL AND status = "In Progress" AND assignee = currentUser()). - When creating issues,
--projectand--typeare required. Common types:Task,Bug,Story,Epic,Sub-task. - When creating or updating issues with
--description, the value must be valid ADF (Atlassian Document Format) JSON. - When adding or updating comments with
--body, the value must be valid ADF JSON. Wrap in single quotes to prevent shell expansion of brackets. - For
get,update, anddeleteon comments,--issueis required to identify which issue the comment belongs to. - Always show the user the command you are about to run before executing it.
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kFAQ
What fields are required to create an issue?
The docs state --project and --type are required; common types are Task, Bug, Story, Epic and Sub-task.
How does search work?
You build a valid JQL query from intent, for example project = PIXEL AND status = "In Progress" AND assignee = currentUser().