wa:confluence-publish

Publish changed Markdown docs from docs/ to Confluence pages.

Updated Mar 26, 2026

Search Tags:#documentation #markdown #publishing #mcp #confluence #frontmatter #incremental sync

Ready to run

npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-confluence-publish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wa:confluence-publish
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/confluence-publish
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-confluence-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the manual process of pushing local documentation into Confluence by automatically publishing only documents that have changed, keeping Confluence and your repository docs in sync.

Core Features & Use Cases

Incremental Confluence publishing: Scans Markdown files under docs/, computes content hashes, and creates or updates Confluence pages only when needed.
Frontmatter-driven control: Reads document frontmatter (including type, status, and stored Confluence page IDs) to decide between create vs update and to manage labeling.
Operational safety and reporting: Requires Confluence to be enabled and verifies MCP connectivity before publishing, then produces a clear success/skip/failure report.
Confluence label mapping: Applies labels based on the doc type using the Confluence API’s native labels parameter.

Quick Start

Run /confluence-publish docs/**/*.md to publish changed Markdown docs from docs/ into your Confluence space.

Frequently Asked Questions about wa:confluence-publish

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

FAQPage Schema

How do I publish Markdown documentation to Confluence automatically?▼

You can publish Markdown documentation to Confluence by scanning files under docs/, computing content hashes, and creating or updating pages only when changes are detected. It requires MCP connectivity and CONFLUENCE_ENABLED gating before executing operations.

How does incremental sync work for Confluence page updates?▼

Incremental sync for Confluence page updates works by computing local content hashes and comparing them against stored metadata. It creates missing pages and updates existing ones only when needed, then records Confluence page IDs and last published metadata in local frontmatter after successful operations.

Can I use frontmatter to control Confluence page creation and labeling?▼

Yes, you can use frontmatter to control Confluence page creation and labeling. The Skill reads document frontmatter, including type and status, to decide whether to create or update a page, and applies labels based on the doc type using the Confluence API’s native labels parameter.

Does Confluence publishing require MCP preflight checks?▼

Yes, Confluence publishing requires MCP preflight checks. The Skill mandates MCP connectivity via core/ops:mcp-preflight and enforces CONFLUENCE_ENABLED gating before attempting to publish any local documentation to ensure operational safety.

What is the best way to test Confluence publishing without making live changes?▼

The best way to test Confluence publishing without making live changes is to use the dry-run mode. This allows you to target specific paths or patterns and preview the success, skip, and failure report without actually creating or updating Confluence pages.

Why are my Confluence pages not updating when I republish my docs?▼

Your Confluence pages may not be updating because the content hashes have not changed, triggering an incremental sync skip. You can use the force mode to override this behavior and update pages regardless of computed content hashes.