custom-pr-summary

To generate a concise PR summary, the Skill reads your feature documentation from the 'features/' directory and uses git commands to detect the current branch. It outputs a brief overview, lists changed files grouped by type, and highlights key files for reviewer focus.

To automatically list changed files in a GitHub pull request, this Skill parses your feature documentation and groups changed files by type. It extracts this information by analyzing the branch's feature docs to provide a ready-to-paste PR description.

Yes, you can generate a PR description directly from feature docs without manually writing summaries. The Skill locates feature documents in the 'features/' directory to automatically extract overviews and identify key review areas.

Generating a pull request summary requires git commands to detect the current branch and locate feature documents in the 'features/' directory. Your repository must contain these feature documents for the Skill to extract the necessary overview and changed file lists.

Using feature documentation to create code review summaries provides essential context upfront, reducing the need for reviewers to sift through lengthy documents. It extracts an overview and highlights key files for reviewer focus directly from the feature specs.

A limitation when extracting a PR overview is that the Skill requires feature documents to be present in the 'features/' directory. Without these documents, it cannot detect the branch context or generate the grouped changed files list for your pull request.