contributor-pr-description

Generate pull request descriptions with structured templates and GitHub CLI identity verification.

2.8k|166|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/flutter/agent-plugins --skill contributor-pr-description
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contributor-pr-description
Source: https://github.com/flutter/agent-plugins/tree/main/tool/dart_skills_lint/.agents/skills/contributor-pr-description
Command: npx skills add https://github.com/flutter/agent-plugins --skill contributor-pr-description

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the inconsistency and lack of context in pull request descriptions, which often leads to delayed reviews and confusion regarding the purpose and verification of code changes.

Core Features & Use Cases

  • Standardized Templates: Enforces a consistent structure including summary, motivation, related issues, and testing instructions.
  • Identity Verification: Ensures the agent verifies GitHub CLI authentication and commit author identity before performing git operations.
  • Use Case: Use this skill when you are ready to submit a feature branch to ensure your PR description is professional, informative, and contains all necessary context for maintainers.

Quick Start

Draft a pull request description for the current branch using the contributor-pr-description guidelines.

Frequently Asked Questions about contributor-pr-description

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

FAQPage Schema
How do I create a standardized pull request description for better code review?

Standardized pull request descriptions require a structured template enforcing sections for summary, motivation, related issues, and testing instructions. This ensures clear context and auditability for maintainers reviewing code contributions.

What should a GitHub pull request description include to pass code review?

A GitHub pull request description should include a summary, motivation, related issues, and testing instructions. Enforcing this structured template ensures clear communication and auditability for code contributions during reviews.

Do I need GitHub CLI authentication to automate PR description generation?

Yes, GitHub CLI authentication is required for PR description generation. The process enforces identity verification protocols to verify GitHub CLI authentication and commit author identity before performing git operations.

When should I use a structured PR template for my code contributions?

Use a structured PR template when submitting a feature branch in software development workflows requiring clear communication and auditability. It ensures your pull request description is professional, informative, and contains necessary context for maintainers.

Why does my pull request description need identity verification for git operations?

Identity verification is needed for git operations to ensure auditability in software development workflows. The protocol verifies GitHub CLI authentication and commit author identity before generating pull request descriptions, preventing unauthorized contributions.

Can I enforce a specific PR documentation format for my repository contributors?

Yes, you can enforce a specific PR documentation format by applying a standardized template. This enforces repository-specific documentation practices, requiring contributors to include summaries, motivations, related issues, and testing instructions.