← ClaudeAtlas

jiralisted

Manage Jira issues via CLI. View, create, update, transition, assign, comment, sprint ops. Use when user mentions issue keys (PROJ-123), tickets, sprints, or keywords like jira/ticket/backlog.
vanducng/skills · ★ 0 · AI & Automation · score 76
Install: claude install-skill vanducng/skills
# Jira Integration (CLI Backend) Uses `jira` CLI (ankitpokhrel/jira-cli). Backend confirmed available at `/opt/homebrew/bin/jira`. ## Defaults - **Default board:** ELT Board - **Token source:** `~/.envrc` — source it before any jira command ## Authentication (MANDATORY — run FIRST) Tokens are stored in `~/.envrc`. **Before any Jira operation**, ask the user which project and export the correct token: | Project | Token env var | Email env var | Atlassian instance | |---------|--------------|---------------|--------------------| | CNB | `JIRA_CNB_API_TOKEN` | `JIRA_CNB_USER_EMAIL` | teamcnb.atlassian.net | | ABS | `JIRA_ABS_API_TOKEN` | `JIRA_ABS_USER_EMAIL` | abspectrum.atlassian.net | **Workflow:** 1. Infer project from issue key prefix (ELT → CNB). Only ask if ambiguous. 2. Source `~/.envrc` and export the chosen token + email + base URL. **IMPORTANT: Always hardcode base URL, do NOT rely on `$JIRA_BASE_URL` env var (it's unset).** ```bash # For CNB: source ~/.envrc && export JIRA_API_TOKEN="${JIRA_CNB_API_TOKEN}" && export JIRA_USER_EMAIL="${JIRA_CNB_USER_EMAIL}" && export JIRA_BASE_URL="https://teamcnb.atlassian.net" # For ABS: source ~/.envrc && export JIRA_API_TOKEN="${JIRA_ABS_API_TOKEN}" && export JIRA_USER_EMAIL="${JIRA_ABS_USER_EMAIL}" && export JIRA_BASE_URL="https://abspectrum.atlassian.net" ``` 3. Prepend `source ~/.envrc && export JIRA_API_TOKEN=...` to ALL subsequent jira CLI and curl commands in the session. ## Activation Triggers Activate when user me