jira

Create and manage Jira tickets from conversational context using acli.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/aubrian-halili/ai-experience --skill jira-aubrian-halili
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira
Source: https://github.com/aubrian-halili/ai-experience/tree/main/.claude/skills/jira
Command: npx skills add https://github.com/aubrian-halili/ai-experience --skill jira-aubrian-halili

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating and managing Jira tickets directly from your conversational context, eliminating the need to switch between tools and manually input information.

Core Features & Use Cases

  • Automated Ticket Creation: Generates Jira tickets (bugs, tasks, stories) based on conversation context and provided arguments.
  • Duplicate Detection: Searches for existing similar tickets before creation to prevent duplicates.
  • Use Case: After discussing a bug in a team chat, you can use this Skill to instantly create a Jira bug ticket with all the relevant details extracted from the conversation.

Quick Start

Use the jira skill to create a bug ticket for the login issue discussed.

Frequently Asked Questions about jira

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

FAQPage Schema
How do I create Jira tickets from a conversation without manual data entry?

Jira tickets are created by parsing conversational context and arguments to generate structured content. The Skill extracts relevant details from your discussion and automatically formats them into bugs, tasks, or stories.

Can I search for existing Jira tickets to avoid creating duplicates?

Yes, duplicate detection searches for existing similar tickets before creation. This prevents redundant entries by checking current issues against the parsed conversational context.

How do I update and manage Jira tickets using conversational commands?

Ticket management supports viewing, updating, and editing existing Jira tickets. The Skill parses your conversational arguments to apply changes while prioritizing user confirmation for actions.

Do I need acli installed to manage Jira tasks through this workflow?

The acli Jira integration is required for full functionality, but the workflow degrades gracefully when unavailable. It operates with guardrails against destructive actions and sensitive data exposure.

What happens if acli is unavailable when I try to create a bug ticket?

The workflow ensures graceful degradation when acli is unavailable. It safely handles the missing dependency without failing abruptly or compromising sensitive data during ticket management.

Why does the Jira ticket creation process ask for confirmation before updating?

User confirmation is prioritized to enforce guardrails against destructive actions and sensitive data exposure. This prevents accidental ticket modifications during automated parsing and editing.