code-overview-to-confluence

To publish a code overview to Confluence, provide a file, directory, symbol, or PR reference along with a valid Confluence destination. The workflow generates a progressive-disclosure summary and posts it directly to the specified page or parent location.

Yes, you can save a codebase summary as a draft in Confluence. The workflow supports both draft and live publish modes, enabling a review-and-edit workflow before final deployment to stakeholders.

You generate code documentation for onboarding by targeting an unfamiliar codebase or PR reference. The tool orchestrates a progressive-disclosure overview and publishes the resulting summary to a user-specified Confluence location.

Yes, you need an Atlassian MCP connection to post code overviews. The process validates Atlassian MCP connectivity and confirms a valid Confluence destination, such as a page URL or space and parent combination, before proceeding.

The best way to keep Confluence documentation synchronized is running the code-overview workflow against updated code targets. It captures the current codebase state and publishes a refreshed summary to your Confluence destination, reducing manual steps.

Yes, you can summarize a pull request and post the review summary to Confluence. Provide the PR reference and a target space with a parent page, then publish the generated overview in either draft or live mode.