# Improve Pull Requests for Faster Reviews

Large or unclear pull requests slow reviews and hide important risks. This skill creates structured descriptions, checklists, risk assessments, and split recommendations from change context.

## Install

```bash
npx skillstore add sickn33/git-pr-workflows-pr-enhance
```

## Metadata

- Status: approved
- Slug: sickn33-git-pr-workflows-pr-enhance
- Skillstore revision: r2
- Version status: missing
- Tree hash: 848acd436e66bb1096a05233aeb94ede62a433a32fb47d09a80ef7117983a15a
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/git-pr-workflows-pr-enhance
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- 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/sickn33-git-pr-workflows-pr-enhance
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-git-pr-workflows-pr-enhance/manifest

## Capabilities

- Summarizes changed files and change statistics from Git diff information.
- Builds structured pull request descriptions covering purpose, changes, testing, dependencies, and breaking changes.
- Generates review checklists tailored to source, test, configuration, documentation, and security changes.
- Estimates review effort, evaluates risk factors, and recommends ways to split large pull requests.
- Produces Mermaid architecture diagrams, test coverage comparisons, and reviewer response templates when relevant.

## Use Cases

- Prepare a Feature Pull Request: Turn a feature diff, commit list, and test results into a focused description and reviewer checklist.
- Plan Reviews for Large Changes: Assess change size and risk, then identify logical pull request splits and review priorities.
- Verify Release Readiness: Compare testing, coverage, dependencies, and documentation before approving a release pull request.

## Prompt Templates

### Create a Pull Request Description

```
Create a clear pull request description for these changes: [summary]. Include purpose, key changes, testing, risks, and a reviewer checklist.
```

### Review a Diff and Commit List

```
Review this pull request diff and commit list: [details]. Group changes by category, identify missing context, and propose a focused review checklist.
```

### Split a Large Pull Request

```
Analyze this large pull request: [diff and statistics]. Estimate review effort, identify risk factors, and recommend logical splits with dependencies between them.
```

### Build a Complete Review Package

```
Compare base and head coverage data, architecture notes, and dependency changes: [details]. Produce a complete review package with evidence-based risks and Mermaid diagrams.
```

## Limitations

- Relies on complete repository context, commit history, and test data supplied by the user or available environment.
- Example analyzers contain placeholder helper functions and are not a complete executable package.
- Generated risk and coverage conclusions require verification with project-specific tools and policies.
- Git operations and branch changes require user approval and a clean, correctly configured repository.

## Best Practices

- Provide the target branch, diff, commit intent, test results, and repository conventions before requesting analysis.
- Verify generated metrics and risk claims against actual Git, coverage, and continuous integration results.
- Keep descriptions factual and link each reviewer concern to a specific change or test.

## Anti Patterns

- Do not publish generated coverage numbers or risk scores without checking their sources.
- Do not combine unrelated changes only to avoid creating multiple pull requests.
- Do not run branch-changing or push commands without confirming the repository state and user intent.

## Security Audit

- Audited at: 2026-07-23T23:41:34.895\+00:00
- Summary: Six static findings are false positives caused by Markdown backticks, path formatting, or a Mermaid code fence. Two Python examples execute Git with an unvalidated branch value split into arguments, creating command-argument injection risk if adopted. No prompt injection, exfiltration intent, or other semantic threat was found.

## Stats

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