update-all-docs

Automating Confluence documentation updates and release notes after PR approval involves consolidating proposed edits into a unified review package. This skill executes validation, presents the changes for human approval, and applies them only after explicit consent to ensure an auditable workflow.

The best way to consolidate documentation edits for review before merging is to aggregate Confluence page updates and release-note drafts into a single package. This approach presents a unified view for human approval, ensuring consistency between docs and release notes before application.

Yes, you can draft release notes from a PR branch and require human approval before applying changes. This skill generates release-note drafts and Confluence edits, presenting a unified review package that only applies updates after explicit user approval is granted.

This documentation workflow supports Confluence pages and PR review validation by executing validation steps on an approved PR branch. It consolidates Confluence edits and release notes, presenting them as a unified package for human review before merging.

If you do not approve the consolidated Confluence edits and release notes, the changes are not applied. The skill ensures that updates to documentation and release notes are executed only after explicit user approval is provided during the unified review step.