ansible-epic-analysis

Ansible Epic Analysis

Performs a read-only pre-build analysis of a Jira Epic (or ANSTRAT). Identifies all requested modules, maps action+info pairs, finds missing counterparts in sibling Epics, and checks whether the platform API supports the missing operations. Platform-agnostic — works for any Ansible collection regardless of target platform.

Usage

/ansible-epic-analysis EPIC-XXX
/ansible-epic-analysis ANSTRAT-XXX

The argument is a Jira ticket key — an Epic, ANSTRAT, or even a single Task (which resolves to its parent Epic).

When to Use

• Before starting a collection build — to understand scope and gaps
• For gap analysis — to find missing info or action module tickets
• For planning — to verify API feasibility before creating tickets

Execution Steps

Follow these steps exactly when this skill is invoked. Do NOT ask the user any clarifying questions about ticket content — research autonomously.

Step 0: Detect Jira CLI Binary

Before running any Jira commands, resolve which CLI binary to use. Check in this order and use the first one found:

1. jira-rh — preferred Red Hat CLI
2. which jira — standard jira on PATH
3. Common binary directories — scan well-known locations for a jira executable

if command -v jira-rh &>/dev/null; then
  JIRA_CMD="jira-rh"
elif JIRA_PATH=$(which jira 2>/dev/null) && [ -x "$JIRA_PATH" ]; then
  JIRA_CMD="$JIRA_PATH"
else
  JIRA_CMD=""
  for dir in /usr/bin /usr/local/bin /usr/local/sbin /home/bin "$HOME/bin" "$HOME/.local/bin"; do
    if [ -x "$dir/jira" ]; then
      JIRA_CMD="$dir/jira"
      break
    fi
  done
  if [ -z "$JIRA_CMD" ]; then
    echo "ERROR: No Jira CLI found (tried jira-rh, jira, common bin paths). Install one and retry."
    exit 1
  fi
fi
echo "Using Jira CLI: $JIRA_CMD"

Use $JIRA_CMD in place of jira-rh for every command in this skill.

Step 1: Parse Input and Detect Ticket Type

Extract the Jira ticket key from the user's message (pattern: [A-Z]+-\d+).