Skill

jira-aipcc-create

Creates Jira issues in the AIPCC project by inferring summary, description, type, component, and optional parent epic from context, confirming with user before using acli CLI via Bash.

Jira

Bash

developer-tools

automation

npx claudepluginhub jeremyeder/ai-helpers-plugin --plugin odh-ai-helpers

Tool Access

This skill is limited to using the following tools:

BashAskUserQuestion

Preview

Create Jira issues in the AIPCC project using the `acli` CLI.

SKILL.md

Similar Skills

jira-aipcc-create

Creates Jira issues in the AIPCC project by inferring summary, description, type, component, and optional parent epic from context, confirming with user before using acli CLI via Bash.

2 tools

odh-ai-helpers

create-jira-issue

Use this skill only when the user explicitly invokes /create-jira-issue to create a new Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Accepts a project key, issue type, summary, optional Markdown body, and optional fields (assignee, priority, labels, components, parent, custom fields). Converts the body to ADF, shows a payload preview, requires explicit confirmation, then POSTs to Jira and returns the new issue key.

2 files3 tools

accelerator

Create Issue

Creates new Jira issues using jirac CLI, extracting project key, issue type, summary, assignee, labels, priority, and custom fields from requests with interactive prompts.

jira

Stats

Stars0

Forks0

Last CommitMar 30, 2026

Used By3 plugins

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Create AIPCC Jira Issue

Create Jira issues in the AIPCC project using the acli CLI.

Prerequisites

acli must be installed and authenticated (acli jira auth)

Implementation

Step 1: Infer Issue Details from Context

Analyze the conversation to determine:

Summary: A concise title (under 100 characters) describing the issue
Description: A Markdown description with relevant context, root cause, fix details, or requirements (use Markdown)
Type: One of the following based on the nature of work
- Bug: problem that impairs or prevents product functions; tracks escaped defects
- Story: action-oriented, smallest unit of work that can be completed within one sprint
- Epic: large user story that needs to be broken down; groups bugs, stories, and tasks to show progress of a larger effort; represents significant deliverable; does not span teams
- Feature: use when tracking capability or well-defined set of functionality delivering business value; can include additions/changes to existing functionality
- Spike: time-bound unit of work representing research-related task; not easy to size
- Initiative: use when capturing internal improvements
- Task: unit of work to be accomplished, not end-user facing
Component: One of the valid AIPCC components:
- PyTorch
- AIPCC Productization
- Accelerator Enablement
- Wheel Package Index
- AI Testing + Workflow Validation
- Model Validation
- Development Platform
Parent Epic (optional): If the user specifies an epic key (e.g. AIPCC-1234), include it as the parent

If any field cannot be confidently inferred, ask the user.

Step 2: Confirm with the User

Present the proposed issue details to the user in a clear format:

I'll create the following AIPCC JIRA issue:

**Type**: Bug
**Component**: Wheel Package Index
**Parent Epic**: AIPCC-1234 (if specified)
**Summary**: Fix duplicate CI pipeline runs
**Description**:
> [description]

Shall I go ahead and create this?

Wait for user confirmation before proceeding. If the user requests changes, adjust accordingly.

Step 3: Create the Issue

Build a JSON file with the following structure.

Important: The description field MUST be in Atlassian Document Format (ADF), not plain text. acli will reject plain text descriptions with an error.

If the user specifies a parent epic, include the parent field in additionalAttributes. This is the only way to set the epic/parent relationship — acli jira workitem edit does not support additionalAttributes or custom fields, so the parent must be set at creation time.

{
  "projectKey": "AIPCC",
  "summary": "<summary>",
  "type": "<type>",
  "description": {
    "version": 1,
    "type": "doc",
    "content": [
      {
        "type": "paragraph",
        "content": [
          {
            "type": "text",
            "text": "<description text>"
          }
        ]
      }
    ]
  },
  "additionalAttributes": {
    "components": [{"name": "<component>"}],
    "parent": {"key": "<EPIC-KEY>"}
  }
}

Omit the parent field from additionalAttributes if no epic is specified.

Write it to a temporary file:

cat > "$(mktemp /tmp/acli-issue-create-XXXX.json)" << 'EOF'
{ ... }
EOF

Create the issue using:

acli jira workitem create --from-json <JSON-FILE>

Step 4: Report Result

On success, acli prints the new issue key and URL. Report this to the user:

Created AIPCC-12345: https://redhat.atlassian.net/browse/AIPCC-12345

Clean up the temporary JSON file after creation.

Error Handling

acli not found: Tell the user to install acli and run acli jira auth
Authentication failure: Tell the user to run acli jira auth
Creation failure: Display the error from acli and suggest checking permissions
Invalid component: Show the list of valid components and ask the user to pick one

Examples

Context-Aware Creation

User: [After discussing a bug fix] Create a JIRA for this
Assistant: [Infers details from conversation, presents for confirmation, creates on approval]

Explicit Request

User: /jira.aipcc-create Bug: selfservice build monitoring flakes
Assistant: [Uses provided info, infers description and component, confirms, creates]

Ambiguous Component

User: File a task for updating the CI pipeline docs
Assistant: I'll create an AIPCC task. Which component does this fall under?
  1. AIPCC Productization
  2. Wheel Package Index
  3. Development Platform
  ...