Is a specification file required for this skill to work?

Yes, the skill reads from 'specs/[name].md' to compare the original intended design with the actual code implementation found in the git diff.

Can this skill track BDD scenario implementation?

Yes, it maps code changes back to the scenarios defined in your spec file to provide a clear status update on which requirements have been met.

Where are the generated documentation files saved?

By default, the documentation is saved as a markdown file in the 'docs/' directory using the naming convention '[spec-name]-changes.md'.

How does the skill identify which files were changed?

The skill analyzes the local git diff to identify modified and newly added files, then summarizes their purpose based on the implementation context.

Does it support UI changes or screenshots?

The output format includes a dedicated section for screenshots and examples, allowing you to easily add visual context to your PR documentation.

PR Documentation Generator

Name: PR Documentation Generator
Author: jagreehal

byjagreehal

Collaboration Tools

Automates the creation of comprehensive pull request documentation by correlating technical git diffs with functional specifications.

About

The pr-docs skill streamlines the handoff between development and code review by automatically synthesizing pull request documentation. By analyzing both the original feature specification and the resulting git diff, it creates a structured markdown report that includes file changes, implementation decisions, trade-offs, and BDD scenario coverage. This ensures that reviewers have immediate context on why changes were made, reducing friction in the code review process and maintaining a high-quality documentation trail for every feature implementation.

Key Features

Standardized markdown output optimized for GitHub/GitLab PRs
Automated spec-to-code correlation for context-aware docs
Detailed git diff analysis and file modification mapping
Architectural decision and technical trade-off documentation
0 GitHub stars
BDD scenario implementation tracking and verification

Use Cases

Accelerating code reviews by providing reviewers with instant implementation context
Verifying feature completion against original BDD specifications before merging
Maintaining a historical record of technical decisions within the repository docs

About

Key Features

Standardized markdown output optimized for GitHub/GitLab PRs
Automated spec-to-code correlation for context-aware docs
Detailed git diff analysis and file modification mapping
Architectural decision and technical trade-off documentation
0 GitHub stars
BDD scenario implementation tracking and verification

Use Cases

Accelerating code reviews by providing reviewers with instant implementation context
Verifying feature completion against original BDD specifications before merging
Maintaining a historical record of technical decisions within the repository docs