git-pull-request_skill

Overview

This skill automates creation of Pull Request content by analyzing git commit logs, branch names, and diffs to produce consistent, review-ready PR descriptions. It follows common commit type and gitmoji conventions to categorize changes and generates review points and a finalized PR markdown file for easy submission.

How this skill works

The agent detects the current branch and infers the target parent branch based on branch naming patterns (features/* → main/develop, hotfix/* → main, default → main). It extracts commit logs and file diffs for the specified range, maps commits to categories using gitmojis and conventional types (feat, fix, docs, etc.), and builds a PR using a standard template. The generated content is saved to a file (for example PULL_REQUEST.md) and presented to the user for review and final use with a platform CLI or UI.

When to use it

• When you ask the agent to create a PR or generate PR content (e.g., "Create a PR", "Write a PR for me").
• When you need a summary of changes between branches or a specific commit range (e.g., commit-hash..HEAD).
• After completing work on feature, hotfix, or develop branches and preparing to merge.
• When you want consistent PR formatting and clear review points for reviewers.
• When you need a saved PR markdown file ready to copy into GitHub/GitLab or use with CLI tools.

Best practices

• Run the skill inside a valid git repository and the intended branch to ensure accurate detection and hashes.
• If your workflow differs, explicitly provide the parent branch or commit range to override automatic detection.
• Keep commit messages consistent with gitmoji or conventional commit types to improve categorization accuracy.
• Omit irrelevant template sections—don’t include empty headers like "Screenshots" or "Breaking Changes" unless applicable.
• Always review and adjust generated review points and checklist items before opening the PR.

Example use cases

• Generate a PR for work on features/login to merge into develop, including a review points section highlighting auth logic changes.
• Summarize fixes from hotfix/password-reset branch into a concise PR with affected files and test instructions.
• Create a PR draft from a commit range (abc123..def456) to document a refactor and list risky areas for reviewers.
• Produce a PULL_REQUEST.md file that can be provided to reviewers or submitted via gh/CLI.
• Convert mixed commit history into categorized sections (Features, Fixes, Docs, Refactor) with corresponding commit hashes.