describe_pr

Generate PR descriptions from repository templates and PR metadata.

2|Updated Feb 9, 2026

Search Tags:#automation #git #template #pr #description #code-review #pull-request

Ready to run

npx skills add https://github.com/SiTaggart/.agents --skill describe-pr-sitaggart

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: describe_pr
Source: https://github.com/SiTaggart/.agents/tree/main/skills/describe_pr
Command: npx skills add https://github.com/SiTaggart/.agents --skill describe-pr-sitaggart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of PR descriptions that conform to a repository's PR template, reducing manual drafting and ensuring consistency across teams.

Core Features & Use Cases

Reads the repository's PR template and uses it to structure new descriptions
Retrieves PR metadata, diffs, and base branch information to enrich descriptions
Updates or saves the generated description to the shared store for reuse and traceability

Quick Start

Run the describe_pr command on the target branch to generate a full PR description and save it to .ai/thoughts/shared/prs/{number}_description.md.

Frequently Asked Questions about describe_pr

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

FAQPage Schema

How do I automate pull request descriptions to match a repository's PR template?▼

Generate PR descriptions by reading the repository's PR template, retrieving metadata and diffs, and composing sections like rationale, changes, and verification to update the PR body automatically.

What is the best way to generate code review context from git diffs?▼

Generate code review context by retrieving git diffs and base branch information, then structuring sections for rationale, changes, verification, and impact to enrich the PR description for multiple workflows.

Can I use a PR template to structure automated pull request descriptions?▼

Yes, you can use a PR template to structure automated descriptions. The process reads the existing template and uses it to structure new descriptions, ensuring consistency across teams and reducing manual drafting.

How do I save a generated PR description to the shared store for reuse?▼

Save a generated PR description to the shared store by running the generation command on the target branch, which stores the final output at .ai/thoughts/shared/prs/{number}_description.md for reuse and traceability.

Does the PR description generation process handle multiple workflows?▼

Yes, the PR description generation process handles multiple workflows by composing sections such as rationale, changes, verification, and impact tailored for different workflow contexts within the repository.

What limitations exist when updating a PR body automatically from a template?▼

The limitation is that the tool updates the PR body only when possible, and otherwise saves the generated description to the shared store, requiring manual application if direct update fails.