pr-description
Generate pull request descriptions from diff analysis
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Menú
Generate pull request descriptions from diff analysis
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Structured code review
Find and load available skills
PR description generation
Spec-faithful implementation for spec-driven development
Architecture and interface design for spec-driven development
Codebase analysis and context gathering for spec-driven development
| name | pr-description |
| description | Generate pull request descriptions from diff analysis |
Generate a clear, reviewer-friendly pull request description by analyzing the diff and commit history. Follow this protocol for consistent output.
Analyze the diff: Read all changed files to understand the scope.
Identify the change type: Classify the PR.
Write the summary: Create 1-3 bullet points.
List the changes: Group modifications by area.
Describe testing: Explain what was verified.
Note breaking changes: Flag anything that affects existing behavior.
## Summary
- <1-3 bullet points describing the change>
## Changes
- <grouped description of modifications>
## Testing
- <what was tested and how to verify>
## Breaking Changes
- <list any breaking changes, or "None">
Keep the description concise and factual. Avoid subjective language. Omit the Breaking Changes section if there are none.