# Write Pull Request Descriptions From Real Changes

Reviewers need clear explanations of changes, testing, and risk. This skill turns Git diffs and commits into structured pull request descriptions grounded in available evidence.

## Install

```bash
npx skillstore add agentkitco/pr-description
```

## Metadata

- Status: approved
- Slug: agentkitco-pr-description
- Version: 1.0
- Author version: 1.0
- Skillstore revision: r1
- Version status: invalid
- Tree hash: c27a38f8cda73de94c47b3d2f80fb9b03c50d6d0a25146edeb52aa6625954af3
- Author: agentkitco
- GitHub username: agentkitco
- License: MIT
- Repository: https://github.com/agentkitco/agentkit-dev-skills/tree/3de707c7875147b65ddff504d86b0d0dbf713fa7/skills/pr-description
- Ref: 743429f75b17204d47661a86b577a575ad67517f
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/agentkitco-pr-description
- Manifest: https://skillstore.pages.dev/api/skills/agentkitco-pr-description/manifest

## Capabilities

- Inspect branch commits, diff statistics, and the actual diff to identify behavior changes.
- Use an existing repository pull request template when available.
- Draft imperative pull request titles under 70 characters.
- Organize descriptions around motivation, changes, review guidance, testing, and rollout risk.
- Report known test commands and results, explicitly identifying testing that was not performed.
- Check draft claims against the diff and ask for missing motivation.

## Use Cases

- Prepare a feature pull request: Turn branch changes into a concise description covering behavior, motivation, testing, and review priorities.
- Document a risky release change: Describe migrations, configuration changes, compatibility concerns, and rollback considerations supported by the diff.
- Improve a contributor submission: Adapt a draft to the repository template and remove unsupported claims before requesting review.

## Prompt Templates

### Draft a basic description

```
Write a pull request title and description for this branch. Inspect the diff and clearly state any missing testing evidence.
```

### Follow the repository template

```
Compare this branch with [base branch] and draft the description using our repository template. Ask me about any missing motivation.
```

### Improve an existing draft

```
Check this PR draft against the commits and diff: [draft]. Remove unsupported claims and highlight review priorities. Include only verified testing details.
```

### Document rollout and review risks

```
Draft a PR description against [base branch], emphasizing migrations, configuration, compatibility, and rollback. Distinguish verified details from missing information. Do not publish it.
```

## Limitations

- Requires repository access and Git tooling to inspect local commits and diffs.
- Cannot establish missing motivation or test results without user input or supporting evidence.
- Does not provide an automated testing workflow or guarantee that changes are correct.
- Does not create a pull request unless explicitly asked.

## Best Practices

- Confirm the base branch and provide the linked issue or business requirement.
- Share exact test commands and observed results, including any checks that were not run.
- Review the draft against the diff before publishing, especially claims about risk and compatibility.

## Anti Patterns

- Inventing motivation, passing tests, or screenshots that are not supported by evidence.
- Replacing behavior-level explanations with an exhaustive list of changed files.
- Creating a pull request without an explicit user request.

## Security Audit

- Audited at: 2026-10-17T19:48:10.85\+00:00
- Summary: All five static findings are false positives involving Markdown formatting, legitimate Git inspection, or screenshot guidance. No evidence found of prompt injection, credential theft, or unauthorized publishing. The skill explicitly requires user permission before creating a pull request.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0