# Create Better GitHub Pull Requests

Pull requests often lose context when titles, summaries, and tests are inconsistent. This skill guides Claude, Codex, and Claude Code to produce structured GitHub PR content.

## Install

```bash
npx skillstore add 1natsu172/github-pr-best-practices
```

## Metadata

- Status: approved
- Slug: 1natsu172-github-pr-best-practices
- Skillstore revision: r1
- Version status: missing
- Tree hash: 35dd5ac03b7483d70e07a7bbb0deebaf38be3e14851af70a140873692d700ab3
- Author: 1natsu172
- GitHub username: 1natsu172
- License: MIT
- Repository: https://github.com/1natsu172/dotfiles/tree/master/.claude/skills/github-pr-best-practices
- Ref: c1fdca50ff516318f65fed0d7f9e82797c5171dc
- 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, network
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/1natsu172-github-pr-best-practices
- Manifest: https://skillstore.pages.dev/api/skills/1natsu172-github-pr-best-practices/manifest

## Capabilities

- Formats PR titles with Conventional Commits types and optional scopes.
- Builds PR summaries and test plans with concise checklist items.
- Supports English and Japanese pull request descriptions.
- Follows existing project pull request templates without changing section order.
- Provides GitHub CLI examples for draft, ready, review, comment, and merge workflows.
- Guides commit analysis from merge base so the full branch is represented.

## Use Cases

- Draft a Feature PR: Create a conventional title, short summary, and practical test plan for a new feature branch.
- Standardize Team Pull Requests: Apply consistent sections, checklists, and Conventional Commits titles across many repositories.
- Prepare Bilingual PR Notes: Generate clear English or Japanese PR descriptions while keeping the same structure and review expectations.

## Prompt Templates

### Create a Simple PR Draft

```
Create a draft GitHub PR description for this change: [describe change]. Use English, a Conventional Commits title, a summary, and a test plan.
```

### Turn Commits Into PR Content

```
Review all commits on this branch from the merge base. Propose a PR title, summary bullets, and test plan that cover the full branch.
```

### Follow a Project Template

```
Use the repository pull request template exactly. Fill each section for this change, keep section order, and mark non-applicable sections as N/A.
```

### Prepare a Complex Bilingual PR

```
Create a Japanese PR description for this multi-commit change. Include background, implementation details, migration notes if needed, and a specific test plan.
```

## Limitations

- It does not inspect repository history unless paired with git tooling.
- It does not run tests, verify CI status, or prove the PR is correct.
- Language examples focus on English and Japanese only.
- GitHub CLI actions require authentication and explicit user approval.

## Best Practices

- Analyze the full branch before writing the title or summary.
- Keep summaries focused on what changed and why it matters.
- Use specific test plan items that reviewers can verify.

## Anti Patterns

- Do not use vague summaries such as updated stuff or fixed things.
- Do not change a repository pull request template without a clear request.
- Do not create or update remote PRs without user confirmation.

## Security Audit

- Audited at: 2026-07-06T01:10:42.158\+00:00
- Summary: The static findings are false positives caused by Markdown examples, documentation links, and checklist text. No evidence found for prompt injection, credential exfiltration, malware behavior, or covert network activity in SKILL.md, REFERENCE.md, or resources/pr-template-examples.md.

## Stats

- Views: 376
- Downloads: 12
- Favorites: 1
- Popularity score: 0