From accelerator
Sets up Jira Cloud integration by verifying credentials against a tenant, discovering projects and custom fields, and caching results as version-controlled JSON. Idempotent for updates.
npx claudepluginhub atomicinnovation/accelerator --plugin acceleratorThis skill is limited to using the following tools:
!`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh`
Manage Jira issues, boards, sprints, projects, and epics using jira-cli. Search with JQL, create, update, assign, transition, and comment from the terminal.
Manages Jira issues: view/create/update tickets, check sprints/backlogs via jira CLI, Atlassian MCP tools, or REST fallback. Activates on Jira keywords or issue keys like PROJ-123.
Share bugs, ideas, or general feedback.
!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh
!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-context.sh init-jira
You are setting up the Jira Cloud integration for this project. Work through the steps below in order, stopping to prompt the user only when a value is missing and cannot be derived from existing configuration.
Read the argument string (if any) and note:
--site <subdomain> — Jira Cloud subdomain override (e.g. atomic-innovation)--email <addr> — Atlassian account email override--refresh-fields — skip steps 1–4; re-run field discovery only--list-projects — print cached projects and exit (no network call)--list-fields — print cached fields and exit (no network call)If --list-projects was requested, run:
${CLAUDE_PLUGIN_ROOT}/skills/integrations/jira/scripts/jira-init-flow.sh list-projects
If --list-fields was requested, run:
${CLAUDE_PLUGIN_ROOT}/skills/integrations/jira/scripts/jira-init-flow.sh list-fields
If --refresh-fields was requested, skip to Step 5 (field discovery only).
Use the site from --site if provided. Otherwise read it from config:
${CLAUDE_PLUGIN_ROOT}/scripts/config-read-value.sh jira.site ""
If still empty, prompt: "Enter your Jira Cloud subdomain (the part before
.atlassian.net, e.g. mycompany):"
Use --email if provided. Otherwise read it from config:
${CLAUDE_PLUGIN_ROOT}/scripts/config-read-value.sh jira.email ""
If still empty, prompt: "Enter your Atlassian account email:"
Run the credential resolver:
${CLAUDE_PLUGIN_ROOT}/skills/integrations/jira/scripts/jira-auth-cli.sh
If it exits non-zero with E_NO_TOKEN, tell the user:
No Jira API token found. Generate one at https://id.atlassian.com/manage-profile/security/api-tokens, then add it to
.claude/accelerator.local.md(which is gitignored):--- jira: token_cmd: "op read op://Work/Atlassian/credential" ---Re-run
/init-jiraonce the token is configured.
Then stop. Do not continue with verification until the token is available.
Run the full initialisation flow (or just verify if re-running mid-setup):
${CLAUDE_PLUGIN_ROOT}/skills/integrations/jira/scripts/jira-init-flow.sh verify
On success, meta/integrations/jira/site.json is written with {site, accountId}.
Print: "Verified as <accountId> on <site>.atlassian.net."
On failure, show the error from jira-request.sh and stop.
Run:
${CLAUDE_PLUGIN_ROOT}/skills/integrations/jira/scripts/jira-init-flow.sh discover
This writes projects.json (project key/id/name) and fields.json (field
id/key/name/slug) atomically. Both files are byte-idempotent — re-running
against an unchanged tenant produces no diff.
If --refresh-fields was requested, run only:
${CLAUDE_PLUGIN_ROOT}/skills/integrations/jira/scripts/jira-init-flow.sh refresh-fields
Run:
${CLAUDE_PLUGIN_ROOT}/skills/integrations/jira/scripts/jira-init-flow.sh prompt-default
If work.default_project_code is already set, this is a no-op. Otherwise the
helper prints the available projects and prompts for a selection. Offer to
write the chosen key to accelerator.md.
Print a summary:
Jira integration initialised:
Site: <site>.atlassian.net
Fields: <N> fields cached (meta/integrations/jira/fields.json)
Projects: <M> projects cached (meta/integrations/jira/projects.json)
Default: <KEY> (work.default_project_code)
Remind the user to commit meta/integrations/jira/{site,fields,projects}.json
so teammates pick up the shared cache without running /init-jira themselves.
!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-instructions.sh init-jira