# Prepare Clear Pull Request Descriptions

Writing complete pull request descriptions from branch changes takes time and often misses important context. This skill reviews Git changes and produces a structured title and description.

## Install

```bash
npx skillstore add byronwilliamscpa/pr-prepare
```

## Metadata

- Status: approved
- Slug: byronwilliamscpa-pr-prepare
- Skillstore revision: r2
- Version status: missing
- Tree hash: bc024f8b2a790db0c8c2a405c53ff53a95cfc33e20f5075ca5e1d7b5dd2b5809
- Author: ByronWilliamsCPA
- GitHub username: ByronWilliamsCPA
- License: MIT
- Repository: https://github.com/ByronWilliamsCPA/fragrance-rater/tree/main/.claude/skills/pr-prepare
- Ref: a39a91716eadede5f4cdefd78178fed4e837a128
- 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/byronwilliamscpa-pr-prepare
- Manifest: https://skillstore.pages.dev/api/skills/byronwilliamscpa-pr-prepare/manifest

## Capabilities

- Inspects Git status, branch commits, changed-file statistics, and the branch diff against the selected base.
- Identifies modified components, purpose, impact, risks, breaking changes, and testing context.
- Creates sections for summary, changes, impact, testing, and optional notes.
- Suggests a pull request title using common conventional commit prefixes.
- Presents a complete description and optional commands for pushing the branch and opening the pull request.

## Use Cases

- Describe a feature branch: Convert a completed feature branch into a structured title and reviewer-focused pull request description.
- Standardize team submissions: Apply consistent summary, impact, testing, and notes sections across pull requests.
- Prepare maintenance changes: Summarize dependency, refactoring, performance, or documentation updates before repository review.

## Prompt Templates

### Prepare my current branch

```
Prepare a pull request title and description for my current branch against main. Keep test items unchecked unless verified.
```

### Use another base branch

```
Prepare this branch against develop. Group changes by component and identify any breaking behavior or required follow-up work.
```

### Focus on a bug fix

```
Prepare a bug-fix pull request. Explain the cause, changed behavior, affected components, regression coverage, and remaining risks.
```

### Build a release-ready description

```
Analyze the branch and prepare a release-ready pull request. Separate verified tests from pending checks, and flag migrations, security effects, and compatibility risks.
```

## Limitations

- Assumes main as the base branch unless the user specifies another branch.
- Uses its built-in format and does not discover a repository pull request template.
- Does not run or verify tests and linting, so checklist status requires confirmation.
- Does not automatically push changes or create the pull request.

## Best Practices

- Confirm the correct base branch before generating the comparison.
- State which tests and checks actually ran, and leave unverified items unchecked.
- Review the generated description for sensitive data, inaccurate claims, and missing reviewer context.

## Anti Patterns

- Do not mark tests as passed without execution evidence.
- Do not use vague summaries that repeat the pull request title.
- Do not include credentials, tokens, personal data, or unrelated secrets from the diff.

## Security Audit

- Audited at: 2026-07-23T11:58:46.972\+00:00
- Summary: All 25 static matches are false positives caused by Markdown formatting or fixed Git inspection commands. The commands use no dynamic user input, and push commands appear only as user-facing suggestions.

## Stats

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