Jira Release Publish

Publish a Jira release draft to create or update a version. Requires preview and approval.

jimweller Updated Sep 17, 2026

Coding & Dev Tools

Install

Press C to copy

$ npx skillmds@latest add jimweller/jira-release-publish

Installs into ~/.claude/skills (or .claude/skills inside a project). Restart Claude Code to pick it up.

Download SKILL.md

＋ Add to collection

README badge

[![SkillMD](https://skillmd.com/badge/jimweller/jira-release-publish.svg)](https://skillmd.com/skills/jimweller/jira-release-publish)

Trust & safety

Audits pending

Not yet audited · commit 8faf1b2

Works with: Claude Code Claude.ai OpenAI Codex +

File contents

Jira Release Publish

Publish a Jira release draft file to create a new version or update an existing version's description.

CRITICAL: Preview Before All Mutations

NEVER execute without showing the user a preview first.

For every publish operation:

Read the draft file
Validate frontmatter completeness
Show preview with exact content
Ask for approval explicitly
Only then execute the command
Update draft file with published status

If the user hasn't approved, DO NOT execute.

Workflow

Read draft file from provided path
Parse frontmatter and body content
Validate required fields (project, version_name, action)
Show preview in box format
Ask for explicit approval
Execute via jira-api.sh version-create or version-update
Update draft with status: published and published_version_id
Return version URL

Input

User provides path to a draft file:

/dataops-assistant:jira-release-publish .jira-release-drafts/20250209-183000-2025-1-0.md

Preview Format

Create Version

+-----------------------------------------------------------+
| PREVIEW: Create Version                                    |
+-----------------------------------------------------------+
| Project: PE                                                |
| Version: 2025.1.0                                          |
| Release Date: 2025-02-15                                   |
| Mark Released: No                                          |
|                                                            |
| Description (first 500 chars):                             |
| -------------------------------------------                |
| ## Release 2025.1.0                                        |
|                                                            |
| Released: 2025-02-15                                       |
|                                                            |
| ### Features                                               |
| - [PE-1234]: Add user authentication flow                  |
| - [PE-1235]: Implement dashboard redesign...               |
+-----------------------------------------------------------+

Update Version

+-----------------------------------------------------------+
| PREVIEW: Update Version                                    |
+-----------------------------------------------------------+
| Project: PE                                                |
| Version: 2025.1.0                                          |
| Mark Released: Yes                                         |
|                                                            |
| New Description (first 500 chars):                         |
| -------------------------------------------                |
| ## Release 2025.1.0                                        |
|                                                            |
| Released: 2025-02-15                                       |
|                                                            |
| ### Features                                               |
| - [PE-1234]: Add user authentication flow...               |
+-----------------------------------------------------------+

Commands

CRITICAL: Always use the bin wrapper. Never call scripts by direct path.

# CORRECT — single unambiguous path
JIRA_API="$HOME/.dataops-assistant/bin/jira-api.sh"

Create Version

# With description from stdin
echo "$description_content" | bash "$JIRA_API" version-create "$project" "$version_name" \
  --description - --md \
  --release-date "$release_date"  # if provided

# With --released flag
echo "$description_content" | bash "$JIRA_API" version-create "$project" "$version_name" \
  --description - --md --released

Update Version

# Update description
echo "$description_content" | bash "$JIRA_API" version-update "$project" "$version_name" \
  --description - --md

# Update and mark released
echo "$description_content" | bash "$JIRA_API" version-update "$project" "$version_name" \
  --description - --md --released

Validation Before Preview

Required Fields

jira_release_version must be "1"
action must be "create" or "update"
project must be present
version_name must be present
status must be "draft" (not already published)

Validation Errors

X Cannot publish: Missing required field 'version_name'.

X Cannot publish: Draft already published (status: published).
   Use a new draft or reset status to 'draft'.

Extracting Body Content

The draft file has YAML frontmatter followed by markdown body:

# Extract body (everything after second ---)
body_content=$(awk '/^---$/{n++; next} n>=2' "$draft_file")

Or in bash:

# Read file content
file_content=$(cat "$draft_file")

# Split on frontmatter delimiter
body_content="${file_content#*---}"  # Remove first ---
body_content="${body_content#*---}"  # Remove second ---
body_content="${body_content#$'\n'}" # Remove leading newline

Post-Publish Updates

After successful publish, update the draft file:

Change status: draft to status: published
Add published_version_id: 12345 (from API response)
Write updated file back

Execution Flow

For Create

# Build command
if [[ -n "$release_date" ]]; then
    date_flag="--release-date $release_date"
else
    date_flag=""
fi

if [[ "$mark_released" == "true" ]]; then
    released_flag="--released"
else
    released_flag=""
fi

# Execute
result=$(echo "$body_content" | bash "$JIRA_API" version-create \
    "$project" "$version_name" \
    --description - --md $date_flag $released_flag)

version_id=$(echo "$result" | jq -r '.version_id')
version_url=$(echo "$result" | jq -r '.version_url')

For Update

if [[ "$mark_released" == "true" ]]; then
    released_flag="--released"
else
    released_flag=""
fi

result=$(echo "$body_content" | bash "$JIRA_API" version-update \
    "$project" "$version_name" \
    --description - --md $released_flag)

version_id=$(echo "$result" | jq -r '.version_id')
version_url=$(echo "$result" | jq -r '.version_url')

Output

Success

Published successfully!

Action: Create Version
Project: PE
Version: 2025.1.0
URL: https://mcghealth.atlassian.net/projects/PE/versions/12345

Draft updated: .jira-release-drafts/20250209-183000-2025-1-0.md

Failure

X Publish failed:

Error: [error message from jira-api.sh]

Draft NOT modified. Fix the issue and try again.

Example Session

User: /dataops-assistant:jira-release-publish .jira-release-drafts/20250209-183000-2025-1-0.md

Response:

+-----------------------------------------------------------+
| PREVIEW: Update Version                                    |
+-----------------------------------------------------------+
| Project: PE                                                |
| Version: 2025.1.0                                          |
| Release Date: 2025-02-15                                   |
| Mark Released: No                                          |
|                                                            |
| Description (first 500 chars):                             |
| -------------------------------------------                |
| ## Release 2025.1.0                                        |
|                                                            |
| Released: 2025-02-15                                       |
|                                                            |
| ### Features                                               |
| - [PE-1234]: Add user authentication flow                  |
| - [PE-1235]: Implement dashboard redesign                  |
|                                                            |
| ### Bug Fixes                                              |
| - [PE-1300]: Fix login timeout issue...                    |
+-----------------------------------------------------------+

Update this version in Jira?

User: Yes

Response:

Published successfully!

Action: Update Version
Project: PE
Version: 2025.1.0
URL: https://mcghealth.atlassian.net/projects/PE/versions/12345

Draft updated: .jira-release-drafts/20250209-183000-2025-1-0.md

Rules

ALWAYS preview before execution - No exceptions
ALWAYS ask for approval - User must explicitly confirm
Validate before preview - Don't show preview if required fields missing
Update draft after publish - Mark as published with version ID
Return URL - User needs to verify the result
Don't modify draft on failure - Only update on success
Check status field - Refuse to publish already-published drafts

---name: jira-release-publishdescription: Publish a Jira release draft to create or update a version. Requires preview and approval.---# Jira Release PublishPublish a Jira release draft file to create a new version or update an existing version's description.## CRITICAL: Preview Before All Mutations**NEVER execute without showing the user a preview first.**For every publish operation:1. **Read** the draft file2. **Validate** frontmatter completeness3. **Show preview** with exact content4. **Ask for approval** explicitly5. **Only then** execute the command6. **Update** draft file with published statusIf the user hasn't approved, DO NOT execute.---## Workflow1. **Read draft file** from provided path2. **Parse frontmatter** and body content3. **Validate** required fields (project, version_name, action)4. **Show preview** in box format5. **Ask** for explicit approval6. **Execute** via jira-api.sh version-create or version-update7. **Update draft** with `status: published` and `published_version_id`8. **Return** version URL---## InputUser provides path to a draft file:```/dataops-assistant:jira-release-publish .jira-release-drafts/20250209-183000-2025-1-0.md```---## Preview Format### Create Version```+-----------------------------------------------------------+| PREVIEW: Create Version |+-----------------------------------------------------------+| Project: PE || Version: 2025.1.0 || Release Date: 2025-02-15 || Mark Released: No || || Description (first 500 chars): || ------------------------------------------- || ## Release 2025.1.0 || || Released: 2025-02-15 || || ### Features || - [PE-1234]: Add user authentication flow || - [PE-1235]: Implement dashboard redesign... |+-----------------------------------------------------------+```### Update Version```+-----------------------------------------------------------+| PREVIEW: Update Version |+-----------------------------------------------------------+| Project: PE || Version: 2025.1.0 || Mark Released: Yes || || New Description (first 500 chars): || ------------------------------------------- || ## Release 2025.1.0 || || Released: 2025-02-15 || || ### Features || - [PE-1234]: Add user authentication flow... |+-----------------------------------------------------------+```---## Commands**CRITICAL: Always use the bin wrapper.** Never call scripts by direct path.```bash# CORRECT — single unambiguous pathJIRA_API="$HOME/.dataops-assistant/bin/jira-api.sh"```### Create Version```bash# With description from stdinecho "$description_content" | bash "$JIRA_API" version-create "$project" "$version_name" \ --description - --md \ --release-date "$release_date" # if provided# With --released flagecho "$description_content" | bash "$JIRA_API" version-create "$project" "$version_name" \ --description - --md --released```### Update Version```bash# Update descriptionecho "$description_content" | bash "$JIRA_API" version-update "$project" "$version_name" \ --description - --md# Update and mark releasedecho "$description_content" | bash "$JIRA_API" version-update "$project" "$version_name" \ --description - --md --released```---## Validation Before Preview### Required Fields- `jira_release_version` must be "1"- `action` must be "create" or "update"- `project` must be present- `version_name` must be present- `status` must be "draft" (not already published)### Validation Errors```X Cannot publish: Missing required field 'version_name'.``````X Cannot publish: Draft already published (status: published). Use a new draft or reset status to 'draft'.```---## Extracting Body ContentThe draft file has YAML frontmatter followed by markdown body:```bash# Extract body (everything after second ---)body_content=$(awk '/^---$/{n++; next} n>=2' "$draft_file")```Or in bash:```bash# Read file contentfile_content=$(cat "$draft_file")# Split on frontmatter delimiterbody_content="${file_content#*---}" # Remove first ---body_content="${body_content#*---}" # Remove second ---body_content="${body_content#$'\n'}" # Remove leading newline```---## Post-Publish UpdatesAfter successful publish, update the draft file:1. Change `status: draft` to `status: published`2. Add `published_version_id: 12345` (from API response)3. Write updated file back---## Execution Flow### For Create```bash# Build commandif [[ -n "$release_date" ]]; then date_flag="--release-date $release_date"else date_flag=""fiif [[ "$mark_released" == "true" ]]; then released_flag="--released"else released_flag=""fi# Executeresult=$(echo "$body_content" | bash "$JIRA_API" version-create \ "$project" "$version_name" \ --description - --md $date_flag $released_flag)version_id=$(echo "$result" | jq -r '.version_id')version_url=$(echo "$result" | jq -r '.version_url')```### For Update```bashif [[ "$mark_released" == "true" ]]; then released_flag="--released"else released_flag=""firesult=$(echo "$body_content" | bash "$JIRA_API" version-update \ "$project" "$version_name" \ --description - --md $released_flag)version_id=$(echo "$result" | jq -r '.version_id')version_url=$(echo "$result" | jq -r '.version_url')```---## Output### Success```Published successfully!Action: Create VersionProject: PEVersion: 2025.1.0URL: https://mcghealth.atlassian.net/projects/PE/versions/12345Draft updated: .jira-release-drafts/20250209-183000-2025-1-0.md```### Failure```X Publish failed:Error: [error message from jira-api.sh]Draft NOT modified. Fix the issue and try again.```---## Example Session**User:** `/dataops-assistant:jira-release-publish .jira-release-drafts/20250209-183000-2025-1-0.md`**Response:**```+-----------------------------------------------------------+| PREVIEW: Update Version |+-----------------------------------------------------------+| Project: PE || Version: 2025.1.0 || Release Date: 2025-02-15 || Mark Released: No || || Description (first 500 chars): || ------------------------------------------- || ## Release 2025.1.0 || || Released: 2025-02-15 || || ### Features || - [PE-1234]: Add user authentication flow || - [PE-1235]: Implement dashboard redesign || || ### Bug Fixes || - [PE-1300]: Fix login timeout issue... |+-----------------------------------------------------------+Update this version in Jira?```**User:** Yes**Response:**```Published successfully!Action: Update VersionProject: PEVersion: 2025.1.0URL: https://mcghealth.atlassian.net/projects/PE/versions/12345Draft updated: .jira-release-drafts/20250209-183000-2025-1-0.md```---## Rules1. **ALWAYS preview before execution** - No exceptions2. **ALWAYS ask for approval** - User must explicitly confirm3. **Validate before preview** - Don't show preview if required fields missing4. **Update draft after publish** - Mark as published with version ID5. **Return URL** - User needs to verify the result6. **Don't modify draft on failure** - Only update on success7. **Check status field** - Refuse to publish already-published drafts

jimweller/davit-dataops-dotfiles/tree/main/dataops-plugin/skills/jira-release-publish commit 8faf1b27ed

Frequently asked questions

npx skillmds@latest add jimweller/jira-release-publish