Jira Release Publish

Publish Jira release drafts to create or update versions after preview approval.

2|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/jimweller/davit-dataops-dotfiles --skill jira-release-publish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Jira Release Publish
Source: https://github.com/jimweller/davit-dataops-dotfiles/tree/main/dataops-plugin/skills/jira-release-publish
Command: npx skills add https://github.com/jimweller/davit-dataops-dotfiles --skill jira-release-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of publishing Jira release versions, ensuring that new versions are created or existing ones are updated accurately and safely. It prevents accidental mutations by enforcing a strict preview and approval workflow.

Core Features & Use Cases

  • Version Creation: Create new Jira versions based on draft release notes.
  • Version Updates: Update the description of existing Jira versions.
  • Safety First: Guarantees a preview and explicit user approval before any changes are made to Jira.
  • Draft Management: Updates the source draft file to reflect the published status and version ID.
  • Use Case: A development team needs to release a new version of their software. They create a draft release note in a markdown file. This Skill allows them to preview the exact Jira version details and description before publishing it to Jira, ensuring accuracy and preventing errors.

Quick Start

Use the jira-release-publish skill to publish the draft release file located at /dataops-assistant/.jira-release-drafts/20250209-183000-2025-1-0.md.

Frequently Asked Questions about Jira Release Publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish a Jira release version from a markdown file?

To publish a Jira release version, the skill reads a markdown draft file, validates frontmatter fields, displays a formatted preview of version details, and executes Jira API commands to create or update the version after explicit user approval.

How do I prevent accidental updates when creating Jira versions?

To prevent accidental updates when creating Jira versions, this automation enforces a strict preview and explicit user approval workflow before executing any Jira API commands for version creation or updates.

Can I update an existing Jira version description using a draft release note?

Yes, you can update an existing Jira version description using a draft release note. The skill validates the draft, previews the changes, and updates the Jira version description upon user approval.

Does the Jira release publishing workflow update the source draft file after publishing?

Yes, the Jira release publishing workflow updates the source draft file after publishing. It writes the published status and version ID back to the draft markdown file upon a successful API execution.

What happens if required frontmatter fields are missing in a Jira release draft?

If required frontmatter fields are missing in a Jira release draft, the skill validation fails and halts the process. It prevents the preview generation and blocks the Jira API execution to avoid publishing incomplete version details.