create-jira-issue

Solid

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.

Code & Development 30 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 88/100

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

Skill Content

# Create Jira Issue !`${CLAUDE_PLUGIN_ROOT}/bin/accelerator config context --skill create-jira-issue --fail-safe` > **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. Create a new Jira issue via `POST /rest/api/3/issue`. Work through the steps below in order. This skill never auto-invokes — it only runs when the user explicitly types `/create-jira-issue`. This skill never synthesises `--body` content from upstream context (issue descriptions, web fetches, prior tool output) without explicit user approval — body content always comes from the user's prompt or a path the user named. ## Two modes This skill accepts **either** a work-item file or the explicit flag set: - **Work-item-file mode** — the argument is a path to a `meta/work/` work item (or resolves to one). The issue summary, body, type, and project are derived from the work item, and the created issue's key is written back into the work item's `external_id`. Use this mode whenever the argument is a work-item file path. Follow the **Work-item-file mode** section below. - **Flag-driven mode** — the argument is the `--project/--type/--summary/…` flag set (no work-item file). Follow **Steps 1–10**. This mode is unchanged and writes nothing back to any file. Both modes share one create contract: r...

Details

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

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

update-jira-issue

Use this skill only when the user explicitly invokes /update-jira-issue to modify an existing Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Accepts an issue key and at least one mutating flag (summary, body, priority, assignee, labels, components, parent, custom fields). Shows a payload preview with explicit set-vs-update label semantics, requires explicit confirmation, then PUTs to Jira.

30 Updated today
atomicinnovation
Code & Development Solid

comment-jira-issue

Use this skill only when the user explicitly invokes /comment-jira-issue to add, list, edit, or delete comments on a Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Subcommands: add (post a new comment), list (fetch all comments with pagination), edit (update an existing comment), delete (remove a comment — irreversible). Write subcommands show a payload preview and require explicit confirmation before calling the API.

30 Updated today
atomicinnovation
Code & Development Solid

attach-jira-issue

Use this skill only when the user explicitly invokes /attach-jira-issue to upload one or more local files as attachments to a Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Shows a preview of what will be uploaded and requires explicit confirmation before POSTing.

30 Updated today
atomicinnovation