Release documenter

Automate Atlassian Confluence release documentation creation with MCP authentication and template substitution.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/siteminder-au/claude-code-dx-plugin --skill release-documenter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Release documenter
Source: https://github.com/siteminder-au/claude-code-dx-plugin/tree/main/skills/release-documenter
Command: npx skills add https://github.com/siteminder-au/claude-code-dx-plugin --skill release-documenter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @siteminder/dx, @anthropic-ai/claude-code.

What problem does it solve?

Creating and updating release documentation in Confluence is a repetitive, manual task prone to inconsistencies. This Skill automates the entire process, ensuring accurate and standardized release notes with minimal effort.

Core Features & Use Cases

  • Confluence Integration: Leverages Atlassian MCP to interact directly with Confluence, creating and updating pages seamlessly.
  • Template-Based Generation: Creates new release pages from predefined templates, automatically filling in system, version, and deployment details.
  • Jira & PVT Updates: Automatically updates Jira Query Language (JQL) queries and PVT test tables based on release versions and code changes.
  • Use Case: After a code release, simply ask "Make a release document for demand-manager" and watch as a new, perfectly formatted Confluence page is generated with all relevant details, saving hours of manual work.

Quick Start

Make a v1.0.0 release document for demand-manager

Frequently Asked Questions about Release documenter

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

FAQPage Schema
How do I automate Confluence release documentation creation?

Automate Confluence release documentation by connecting to your repository and Confluence workspace via MCP, specifying the system and version, and letting the Skill generate a formatted page from templates with semantic versioning, Jira updates, and deployment metadata automatically filled in.

Can I use Confluence templates for release notes with Jira integration?

Yes. Template-based release page generation automatically substitutes system, version, and deployment details, then updates Jira Query Language queries and PVT test tables based on the release version and code changes from your repository's master branch and latest tag.

What do I need to set up before creating a release document?

Workspace discovery and MCP authentication to Confluence and your repository are required prerequisites. The Skill resolves versions from the master branch and latest tag, so your repository must be accessible and properly tagged for semantic versioning.

Does this work with Atlassian Confluence and Jira?

Yes. The Skill leverages Atlassian MCP to create and update Confluence pages directly, automatically updates Jira fields and JQL queries, and applies release metadata alongside page creation for end-to-end Atlassian workspace integration.

How does semantic versioning work in release documentation?

Release documentation uses semantic versioning from your repository's latest tag to populate version fields in Confluence pages and Jira updates, ensuring consistent version references across release notes, metadata, and tracking systems.

What happens if my repository lacks proper version tags?

Version resolution depends on semantic tags in your repository. Without properly tagged releases on the master branch or as the latest tag, the Skill cannot reliably populate version fields, potentially resulting in incomplete or generic release documentation.