update-docs

Analyze PR diffs to identify affected Confluence pages and propose edits.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/seanwachs/cursor-skills --skill update-docs-seanwachs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-docs
Source: https://github.com/seanwachs/cursor-skills/tree/main/.agents/skills/update-docs
Command: npx skills add https://github.com/seanwachs/cursor-skills --skill update-docs-seanwachs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and plans updates to Confluence documentation pages affected by a PR. It analyzes diffs, highlights impacted pages, and suggests precise edits to keep docs in sync with code changes.

Core Features & Use Cases

  • Automated change detection: Scans diffs against the main branch to find affected Confluence pages.
  • Targeted edit proposals: Generates concise edit recommendations for each impacted page, reducing review time.
  • Approval-driven deployment: Outlines a step-by-step workflow and requires explicit approval before applying changes.

Quick Start

Run this skill on an approved PR branch to identify Confluence pages affected and propose targeted edits.

Frequently Asked Questions about update-docs

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

FAQPage Schema
How do I automatically update Confluence documentation based on PR changes?

To update Confluence documentation based on PR changes, this Skill analyzes code diffs against the main branch, identifies affected pages, and proposes targeted edits while awaiting human approval before applying changes.

How does diff analysis identify which Confluence pages need editing?

Diff analysis identifies affected Confluence pages by scanning PR changes and mapping them against related documentation catalogs within the Agents Confluence space, such as infrastructure, API, and developer guides.

Can I sync developer guides and API docs with code changes without manual review?

You cannot sync developer guides and API docs without manual review, because this documentation workflow requires explicit human approval of the proposed targeted edit steps before applying any changes to Confluence.

What is the best way to keep infrastructure documentation in sync with approved PR branches?

The best way to keep infrastructure documentation in sync is running this Skill on an approved PR branch to generate concise edit recommendations for impacted Confluence pages, reducing manual review time.

Does this documentation workflow automatically apply edits to the Confluence space?

This documentation workflow does not automatically apply edits to the Confluence space, as it uses an approval-driven deployment model that outlines step-by-step update workflows and requires explicit approval before applying changes.

When should I use an automated Confluence update workflow for PR diffs?

You should use an automated Confluence update workflow for PR diffs when you need to map code changes across infrastructure, API, and developer guide catalogs to prevent documentation drift and reduce manual update effort.