wa:confluence-reconcile

Detect and reconcile drift between local markdown files and Confluence pages.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-confluence-reconcile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wa:confluence-reconcile
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/confluence-reconcile
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-confluence-reconcile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill detects and resolves documentation drift between your local docs and the corresponding Confluence pages, preventing mismatches that waste time and cause confusion during collaboration.

Core Features & Use Cases

  • Drift detection with hashing: Compares local docs/ markdown files against Confluence page content (including frontmatter hash tracking) to classify documents as in-sync, local-ahead, confluence-ahead, both-changed, local-only, or confluence-only.
  • Configurable sync direction: Supports push (default), pull, or bidirectional reconciliation, with policy guardrails that avoid unintended overwrites.
  • Guided conflict resolution: Presents diffs and prompts you to choose which version to keep when both sides have changed.

Quick Start

Run /confluence-reconcile --dry-run to review the drift report before applying any changes.

Frequently Asked Questions about wa:confluence-reconcile

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

FAQPage Schema
How do I detect documentation drift between local markdown and Confluence?

You can preview drift detection by running a dry-run command to generate a report comparing local markdown files against Confluence pages. This review step happens before any changes are applied, allowing you to see which documents are out of sync safely.

Do I need MCP connectivity enabled to sync markdown files with Confluence?

Yes, MCP connectivity is required alongside Confluence enablement to perform documentation reconciliation. These prerequisites allow the system to access your Confluence space, classify document drift, and apply staged push or pull updates.

What is the best way to resolve sync conflicts when both local and Confluence docs have changed?

The best way to resolve sync conflicts is through guided conflict resolution, which presents diffs and prompts you to choose which version to keep. Policy guardrails ensure that unintended overwrites are avoided when both sides have changed.

Can I configure the sync direction for markdown reconciliation to pull from Confluence?

Yes, markdown reconciliation supports configurable sync directions including push (default), pull, or bidirectional updates. You can pull Confluence-ahead content to local docs or push local-ahead changes to Confluence based on your workflow needs.

How does content hashing work for tracking Confluence page updates?

Content hashing works by generating and tracking hashes in the frontmatter of local markdown files. These hashes are cross-referenced with Confluence page content to determine if documents are in-sync or if drift has occurred, keeping bookkeeping of the final state.