init-jira

Solid

Set up the Jira Cloud integration for this project. Verifies credentials against a real Jira Cloud tenant, discovers the tenant's custom-field catalogue and project list, and persists the results under `<paths.integrations>/jira/` (default `.accelerator/state/integrations/jira/`) as team-shared, version-controlled JSON caches. Idempotent: safe to re-run after credential or project changes.

AI & Automation 19 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
43
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Init Jira !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh` !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-context.sh init-jira` > **Configuration**: Set `work.integration: jira` and > `work.default_project_code: <KEY>` in `.accelerator/config.md` to > enable auto-scoping. See the > [`### work` section of `configure/SKILL.md`](../../config/configure/SKILL.md#work) > for the full reference. 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. ## Step 0: Parse arguments 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). ## Step 1: Resolve site Use the site from `--site` if provided. Otherwise read it from config by running `${CLAUDE_P...

Details

Author
atomicinnovation
Repository
atomicinnovation/accelerator
Created
2 months ago
Last Updated
today
Language
HTML
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

jira

Fetches and optimizes context from a JIRA issue for AI-assisted development. Searches assigned issues or fetches by key. Distills title, description, acceptance criteria, sprint context, and comments into a structured task description. Analyzes the codebase to surface missing criteria, scope, and risks. Optionally enriches the JIRA issue with a structured analysis comment, and for Complex-scope work can spawn implementation tickets in JIRA. Re-running on the same key refreshes the local task with the latest JIRA state instead of overwriting prior enrichment. Use before /optimus:tdd, /optimus:brainstorm, or /optimus:branch to pull task context from JIRA, or to refresh existing context after JIRA edits.

58 Updated yesterday
oprogramadorreal
AI & Automation Listed

jira

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.

0 Updated today
vanducng
Code & Development Solid

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.

19 Updated today
atomicinnovation