attach-jira-issue

Solid

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.

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

# Attach files to a Jira Issue !`${CLAUDE_PLUGIN_ROOT}/bin/accelerator config context --skill attach-jira-issue --fail-safe` Upload one or more local files as attachments to a Jira issue. Work through the steps below in order. This skill never auto-invokes — it only runs when the user explicitly types `/attach-jira-issue`. ## Step 1: Parse flags Required: - `KEY` — issue key (first positional), e.g. `ENG-42` - `FILE [FILE...]` — one or more local file paths to upload Optional flags: - `--quiet` — suppress INFO stderr lines ## Step 2: Generate the describe preview Invoke the flow script with `--describe`: ``` ${CLAUDE_PLUGIN_ROOT}/skills/integrations/jira/scripts/jira-attach-flow.sh \ --describe <KEY> <FILE> [FILE...] ``` File validation runs before `--describe` returns, so missing or unreadable files surface here as exit 132, before any confirmation is shown. ## Step 3: Handle preview failures - **Exit 132 (`E_ATTACH_FILE_MISSING`)**: tell the user: > File not found or not readable: `<path>`. Check the path and try again. Stop — do not proceed to confirm. - **Exit 133 (`E_ATTACH_BAD_FLAG`)**: tell the user: > Unrecognised flag. Usage: `/attach-jira-issue ISSUE-KEY FILE [FILE...] [--quiet]` Stop. - **Other non-zero**: tell the user "Preview failed — no API call was made." Stop. ## Step 4: Render the preview Show under this heading: > **Proposed Jira write — review before sending** Content: - Endpoint: `POST /rest/api/3/issue/<KEY>/attachments` - ...

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

attach-linear-issue

Use this skill only when the user explicitly invokes /attach-linear-issue to attach a link or a binary file to an existing Linear issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Link mode registers an external URL; binary mode uploads a local file via Linear's pre-signed URL flow and registers the resulting asset. Shows a preview, requires explicit confirmation, then attaches.

30 Updated today
atomicinnovation
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.

30 Updated today
atomicinnovation
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