pr-description

Write semantic pull request titles and structured bodies with diff statistics and risk analysis.

6|6|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/intent-hq/cloudlands-fe --skill pr-description-intent-hq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-description
Source: https://github.com/intent-hq/cloudlands-fe/tree/main/.agents/skills/pr-description
Command: npx skills add https://github.com/intent-hq/cloudlands-fe --skill pr-description-intent-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull request descriptions are often vague, missing verification evidence, or lacking risk context, which slows down code review and lets unverified claims slip through. This Skill produces reviewer-ready PR titles and bodies grounded in the actual diff and the commands that were really run. ## Core Features & Use Cases - Semantic Titles: Generates CI-compliant type(scope): imperative subject titles using the exact accepted types (feat, fix, chore, docs, refactor, test, ci, perf). - Structured Body Sections: Enforces Summary with exact diff statistics, What Changed, Architecture, Testing, What's NOT Changed, and a P0-P3 Risk Analysis with a summary table. - Verification Discipline: Requires exact test commands and results from git diff --stat, vitest, tsc, lint, and Playwright runs, forbidding invented metrics or unverified claims. - Use Case: After finishing a feature branch, ask for a PR description and receive a complete title and body with real diff numbers, the tests actually executed, and a risk mapping reviewers can act on. ## Quick Start Write a pull request title and body for my current branch changes following the pr-description skill.

Frequently Asked Questions about pr-description

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

FAQPage Schema
How do I write a good pull request description?▼

A good PR description states the exact scope, evidence, and risk. Include a summary with real diff statistics, grouped changes, architecture context, the exact test commands run with results, out-of-scope boundaries, and a P0-P3 risk analysis with concrete test steps.

What is a semantic PR title format?▼

A semantic PR title uses the form `type(scope): imperative subject`, where type is one of feat, fix, chore, docs, refactor, test, ci, or perf. The subject is concise, imperative, lowercase-typed, and does not end with a period.

How do I get exact diff statistics for a PR summary?▼

Run `git diff --stat` on the final diff to get files changed and line totals, and use `git diff --numstat` to verify insertion and deletion counts. Include the exact numbers, including zeroes, rather than estimating.

What should a PR risk analysis include?▼

Map every modified component, IPC handler, or state migration to a user-facing feature across P0 (critical) through P3 (low) levels. Each risk item needs at least one concrete automated or manual test step, and the section ends with a summary table of counts per level.

When can the Results section be omitted from a PR body?▼

Omit the Results section only when no meaningful before/after metric exists, such as line counts, IPC calls, render counts, bundle size, latency, or memory. Never manufacture metrics to fill the section.