skills.rest
easingthemes
easingthemesCOMMUNITY
Explore all skills by this author →
Website𝕏@draganfillGitHub

dx-doc-retro

Generate wiki-ready documentation from ADO work items, PRs, and code changes.

6|3|Updated Mar 21, 2026
Search Tags:#documentation#codebase#pr#wiki#confluence#ado#retroactive
One-click install
npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-doc-retro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dx-doc-retro
Source: https://github.com/easingthemes/dx-aem-flow/tree/main/plugins/dx-core/skills/dx-doc-retro
Command: npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-doc-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate comprehensive retroactive documentation for completed stories by aggregating ADO work item data, linked PRs, and codebase insights to produce wiki-ready pages without requiring pre-existing spec files.

Core Features & Use Cases

  • Fetch ADO work item details (title, state, iteration) and related PRs
  • Search the codebase for changed files and patterns informed by the story and PRs
  • Post to either ADO Wiki or Confluence depending on provider config
  • Support retroactive documentation when documentation was never produced during development

Quick Start

Provide an ADO work item ID or URL to generate retroactive documentation for the associated story.

Frequently Asked Questions about dx-doc-retro

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

FAQPage Schema
How do I generate retroactive documentation for completed ADO stories?▼

Generate retroactive documentation by providing an ADO work item ID or URL to fetch story details, aggregate linked PR metadata, search codebase changes, and post wiki-ready pages automatically.

Can I post generated technical documentation to Confluence from Azure DevOps work items?▼

Yes, you can post generated technical documentation to Confluence from Azure DevOps work items by configuring the provider settings, with ADO Wiki available as an alternative backend.

What is retroactive codebase documentation and when do I need it?▼

Retroactive codebase documentation generates wiki-ready technical pages for completed stories after development ends, needed when documentation was never produced during the active development cycle.

Do I need pre-existing spec files to generate wiki documentation from PRs?▼

No, you do not need pre-existing spec files to generate wiki documentation from PRs, because the process applies a fallback mechanism aggregating work item data and codebase insights directly.

How does automated documentation aggregate codebase insights from pull requests?▼

Automated documentation aggregates codebase insights by fetching ADO work item details, collecting linked PR metadata, and searching the codebase for changed files and patterns informed by the story.

What are the limitations of auto-generating wiki pages from ADO work items?▼

Limitations of auto-generating wiki pages include depending on accurate ADO work item data and linked PR metadata to search codebase changes effectively without pre-existing spec files.

Related Skills

Explore More Software Engineering Skills→
MostAshrafMostAshraf
11

pr-creator

Create pull requests across ADO, GitLab, GitHub, and Jira with branch validation and work-item linking.

Community
Advanced
easingthemeseasingthemes
6

dx-doc-gen

Generate wiki documentation from spec files and publish to ADO Wiki or Confluence.

Community
Advanced
osouthgateosouthgate
4

diff-summary

Classify git diff files by role and risk into structured summaries.

Community
Intermediate
easingthemeseasingthemes
6

dx-pr-reviews-report

Automates categorized PR review reports and posts them to ADO Wiki or Confluence.

Community
Intermediate