Git PR Helper

Generate pull request titles and bodies from branch changes.

When to use this skill

• The user is about to open a pull request
• The user asks for a PR title or PR body
• A PR description is requested

Workflow

1. Review the branch changes and recent commits.
2. Identify the primary intent, scope, and impact of the change.
3. Draft a concise PR title in imperative mood.
4. Draft a PR body using the standard sections below.
5. Ask if any context, validation, or notes should be adjusted.

PR title guidelines

• Use imperative mood ("add", "fix", "update")
• Keep it concise (max 72 characters)
• Describe what and why, not how
• No trailing period

PR body format

## Summary
- <1-3 bullet points of the change>

## Validation
- <tests or checks run, or "Not run">

## Notes
- <optional context, risks, or follow-ups>

Examples

Feature PR

Title:

add skill validation workflow for branches

Body:

## Summary
- add GitHub Actions workflow to validate skills
- run checks on pushes and pull requests

## Validation
- Not run (CI only)

## Notes
- None

Fix PR

Title:

fix workflow output delimiter for validation report

Body:

## Summary
- fix multiline output formatting for report step

## Validation
- Not run (CI only)

## Notes
- None

Refactor PR

Title:

refactor skill templates for clearer examples

Body:

## Summary
- reorganize sample skills for readability
- align examples with current conventions

## Validation
- Not run (docs only)

## Notes
- None

Output expectations

• Provide a PR title and full PR body.
• Keep the summary factual and concise.