atlassian-content

Create and repair Jira and Confluence content with deployment-specific formats.

18|9|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/arozumenko/sdlc-skills --skill atlassian-content
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atlassian-content
Source: https://github.com/arozumenko/sdlc-skills/tree/main/skills/atlassian-content
Command: npx skills add https://github.com/arozumenko/sdlc-skills --skill atlassian-content

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Atlassian Jira and Confluence do not reliably render markdown the way people expect, and formatting drift often slips in after creation.

Core Features & Use Cases

  • Correct format by deployment and surface: Generates the right body format for Jira Cloud (ADF), Jira Server/Data Center (wiki markup), and Confluence (storage format).
  • Identity-safe mentions: Uses the correct mention identifiers per deployment (accountId for Cloud; username/userKey for Server).
  • Verification-first reliability: Re-fetches what was created and validates rendered output, then repairs formatting drift when needed.
  • Raw-fetch before updates: For edits, fetches the raw structured body first (ADF/wiki/storage) and merges changes instead of overwriting structure.

Quick Start

Use the atlassian-content skill by running: npx github:arozumenko/sdlc-skills init --skills atlassian-content.

Frequently Asked Questions about atlassian-content

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

FAQPage Schema
How do I format Jira and Confluence content so it renders correctly without formatting drift?

To format Jira and Confluence content correctly, generate deployment-specific body formats like ADF for Jira Cloud, wiki markup for Server, and storage format for Confluence, then verify rendered output and repair drift via PUT/PATCH calls.

Does Jira Cloud use the same wiki markup as Jira Server for issue comments and mentions?

No, Jira Cloud uses Atlassian Document Format (ADF) and accountId for mentions, while Jira Server/Data Center uses wiki markup and username/userKey identifiers to render issue comments and mentions correctly.

What is the best way to update an existing Confluence page without overwriting its storage format structure?

The best way to update Confluence pages safely is raw-fetching the existing storage format body first, then merging your changes into that structured content instead of overwriting it during the update.

Why does my Jira issue formatting break after posting markdown through the API?

Jira issue formatting breaks because Jira does not reliably render standard markdown; it requires ADF or wiki markup depending on deployment, and formatting drift can slip in after creation requiring post-creation verification and repair.

Can I use standard markdown to file bugs and author Confluence runbook pages with mentions?

No, standard markdown does not reliably render in Atlassian tools; filing bugs and authoring runbook pages requires correct body formats like ADF or storage format, plus identity-safe mention identifiers per deployment to render properly.

How do I prevent formatting drift when leaving review comments in Jira?

Prevent formatting drift in Jira review comments by generating deployment-specific body formats, then re-fetching the created content to validate the rendered output and repairing any drift via appropriate PUT or PATCH calls.