document-feature

To generate feature documentation from a pull request, use a command with the PR number to extract metadata, changed files, and linked issues into a structured Markdown document. It reads the PR data to produce publish-ready text covering overview, usage, and use cases.

Automating release notes creation from merged PRs involves reading PR titles, bodies, and acceptance criteria to output structured Markdown. This process transforms code changes into publish-ready wiki pages or release summaries with sections like Getting Started and How It Works.

Yes, you can create wiki pages from code changes using just a feature name. The workflow supports both PR-number and feature-name inputs to analyze code changes and generate structured Markdown documentation suitable for internal wikis or user-facing guides.

Auto-generated feature docs include structured sections such as Overview, Getting Started, How It Works, Options, and Use Cases. These sections are populated by analyzing PR metadata, changed files, and linked issues to ensure comprehensive coverage of the feature.

Generating PR-based documentation does not strictly require linked issues, but it reads them when available. It primarily uses PR titles, bodies, and changed files to produce the Markdown document, incorporating linked issues to enrich the acceptance criteria and use cases.