Create GitHub Pull Request From Specification

Feature specifications need translation into pull request descriptions with implementation details, testing evidence, and review guidance. This skill analyzes specifications and code changes to generate comprehensive PR descriptions including change summaries, testing approaches, deployment considerations, and reviewer instructions for efficient code review.

What Is This?

Overview

Create GitHub Pull Request From Specification converts feature specs into structured PR descriptions. It summarizes implemented changes, explains technical approach, documents testing performed, lists affected components, identifies potential risks, provides reviewer guidance, links related issues, and formats using PR templates.

The skill communicates code changes effectively by highlighting what changed, why changes were necessary, how implementation was tested, and what reviewers should focus on.

Who Should Use This

Developers creating pull requests. Technical leads reviewing code. Open source contributors submitting changes. Teams maintaining PR quality standards. DevOps engineers documenting infrastructure changes. Junior developers learning PR best practices.

Why Use It?

Problems It Solves

Poorly described PRs lack context, causing confusion during review. Generated descriptions provide complete information reviewers need upfront.

Developers often forget to document testing approaches. This skill ensures testing coverage is explicitly described in the PR body.

Reviewers waste time understanding change scope. Clear summaries and component lists focus review efforts efficiently.

PRs missing deployment considerations cause production issues. Generated descriptions surface deployment risks and rollback procedures.

Core Highlights

Change summary generation from specification. Technical approach documentation. Testing evidence description. Affected component identification. Risk and consideration highlighting. Reviewer guidance and focus areas. Related issue linking. PR template formatting.

How to Use It?

Basic Usage

Provide a feature specification and implementation summary. The skill generates a PR description ready to paste when creating a pull request.

Create PR description for OAuth implementation
following this specification:
[Paste spec]

Generate pull request description for bug fix
adding input validation to prevent XSS

Specific Scenarios

For feature PRs, emphasize implementation approach.

Create PR description explaining how we implemented
real-time notifications using WebSockets

For refactoring PRs, highlight structural changes.

Generate PR description for extracting shared logic
into reusable utility functions

For infrastructure PRs, focus on deployment steps.

Create PR description for Kubernetes configuration
with rollout strategy and rollback procedure

Real World Examples

A developer implements an authentication feature following a product specification. Using this skill, the specification is analyzed and the PR description summarizes the added OAuth2 login flow with token refresh, explains the technical approach using an existing auth library, documents testing including unit tests for token handling and integration tests for the login flow, lists affected components, notes a deployment consideration for database migration, provides reviewer guidance to focus on token security, and links to the related feature issue. Review proceeds efficiently with complete context.

A senior developer refactors complex legacy code. The generated PR description explains the motivation around testability and maintainability, summarizes structural changes extracting business logic from controllers, documents preserved behavior through a comprehensive test suite, highlights areas where logic was clarified versus changed, and guides reviewers to verify test coverage completeness.

An infrastructure engineer updates Kubernetes deployment configuration. The skill generates a PR description documenting changes to resource limits and health checks, explains reasoning based on observed memory usage patterns, describes staging environment load tests, identifies rollback procedures, lists post-deployment monitoring metrics, and provides a reviewer checklist covering security and resource considerations.

Advanced Tips

Include screenshots or recordings for UI changes. Link to design documents for context. Mention breaking changes prominently. Use checklists for reviewer verification. Tag specific reviewers for different aspects. Include performance benchmark results if relevant. Update PR descriptions as review feedback clarifies details.

When to Use It?

Use Cases

Feature implementation pull requests. Bug fix documentation. Refactoring explanations. Infrastructure change proposals. API endpoint additions. Database migration PRs. Security patch descriptions. Performance optimization PRs.

Related Topics

Code review best practices. Pull request templates. Technical writing for developers. Change documentation standards. Software testing documentation. Deployment risk management. Version control workflows.

Important Notes

Requirements

Clear feature specification or change description. Understanding of implementation approach. Knowledge of testing performed. Awareness of affected system components. Deployment considerations if applicable.

Usage Recommendations

Write PR descriptions when creating the pull request. Include all relevant context upfront. Document testing thoroughly. Highlight security or performance implications. Link related issues and PRs. Use consistent formatting across PRs. Update descriptions as review progresses.

Limitations

Quality depends on specification completeness. Cannot verify implementation matches description. Requires accurate testing information from the developer. Should be supplemented with good commit messages. May need customization for team conventions.