# Pr Description

> Write a clear, useful PR description — a tight Why / How / Decisions / Callouts structure that tells a reviewer what changed and why, with no filler. Use whenever you open or rewrite a pull request.

- **Type:** Skill
- **Install:** `agentstack add skill-shivaedev-pardes-pr-description`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [ShivaeDev](https://agentstack.voostack.com/s/shivaedev)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [ShivaeDev](https://github.com/ShivaeDev)
- **Source:** https://github.com/ShivaeDev/pardes/tree/main/plugins/pr-description/skills/pr-description

## Install

```sh
agentstack add skill-shivaedev-pardes-pr-description
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# pr-description

A good PR description answers three things fast: *why does this exist, what did it do, and what should I look at?* Use this exact structure, and keep every section short — a reviewer should grasp the change in under a minute.

## Title

Meaningful, and about impact — what the change does for the product or system, not how it's implemented. Never a branch name, a file path, or "fix stuff".

## Body

### Why?

1–3 sentences: the actual problem or motivation. Pull it from the real context; don't invent one. If you genuinely don't know why, find out before opening the PR.

### How?

1–2 sentences: a short technical summary for a technical reader — the approach, not a file-by-file walkthrough.

### Decisions

One bullet per meaningful tradeoff, abandoned alternative, or scope choice — each with the reason. `N/A` if there were none.

### Callouts

One bullet per spot a reviewer should look harder at — risky surfaces, things that look innocuous but have knock-on effects, one-way doors. `Callouts — N/A` if everything is straightforward.

## Never include

- **Files-changed lists** — the diff already shows them.
- **Test plans** or "how I tested" narration.
- **Risk speculation** and hedging.
- **Diff narration** — restating the code change in prose.

That's it: an honest title, four short sections, and nothing the diff already says.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [ShivaeDev](https://github.com/ShivaeDev)
- **Source:** [ShivaeDev/pardes](https://github.com/ShivaeDev/pardes)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-shivaedev-pardes-pr-description
- Seller: https://agentstack.voostack.com/s/shivaedev
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.