How is the PR title and body generated?

The tool uses the plan_*.md guidance and commit history to produce a descriptive title in the format 'Feature: ...' and a multi-section body.

Can I customize the PR title or body?

Yes, you can provide an optional title/description hint via the [title] argument to tailor the generated PR.

What happens if there are no meaningful changes compared to origin/main?

If no changes are detected, review diffs and confirm with the user; the PR should reflect intentional changes, so you may need to adjust the branch or guidance accordingly.

pr-create

npx machina-cli add skill YoniChechik/claude-code-config/pr-create --openclaw

Files (1)

SKILL.md

1.3 KB

Creates a professional pull request when a feature is complete and ready for review.

Optional PR title/description hint from user input

"$ARGUMENTS"

Process

Step 1: Analyze Feature Branch

Compare to origin/main:

git log origin/main..HEAD --oneline
git diff origin/main...HEAD --stat

Erase plan_*.md and any other dev/workflow related files and commit. If not sure, ask user for directions.

Step 2: Generate PR Title and Body

Create professional PR content:

Title Format: Feature: [Descriptive title based on plan_*.md and commits]

Body Structure:

## Summary
- Key functionality delivered
- Major components implemented
- Value provided to users

## Implementation Details
- Technical approach and architecture decisions
- Integration points with existing codebase
- Notable patterns or utilities used

## Testing
- Unit tests added for core functionality
- Integration tests for end-to-end workflows
- Manual testing performed

Step 3: Create Pull Request

gh pr create --title "Feature: [Generated title]" --body "$(cat <<'EOF'
[Generated PR body]
EOF
)"

Step 4: PR Success Confirmation

Display created PR URL

Source

git clone https://github.com/YoniChechik/claude-code-config/blob/main/skills/pr-create/SKILL.mdView on GitHub

Overview

This skill automates creating a professional GitHub pull request from a feature branch. It analyzes differences against origin/main, suggests a polished title and body, and opens the PR via the GitHub CLI. Using it helps ensure consistency across PRs and speeds up code reviews.

How This Skill Works

It compares your feature branch to origin/main to surface changes, cleans up dev/workflow files if needed, and constructs a standardized PR title and body. It then uses gh pr create with the generated content and reports the PR URL for easy access.

When to Use It

When a feature branch is ready for review and merge
After implementing major components or fixes on a branch
When you want a consistent PR title/body format across the team
When preparing to propose changes that touch multiple modules
When you need to automate PR creation to streamline CI workflows

Quick Start

Step 1: Analyze feature branch vs origin/main: git log origin/main..HEAD --oneline && git diff origin/main...HEAD --stat
Step 2: Generate PR title/body using the plan_*.md guidance and commits
Step 3: Create PR: gh pr create --title "Feature: [Generated title]" --body "$(cat <<'EOF'\n[Generated PR body]\nEOF\n)"

Best Practices

Update the feature branch against origin/main before creating the PR
Use a descriptive plan_*.md to guide the PR content
Ensure the PR title is clear and the body documents functionality, architecture, and testing
Remove plan_*.md and any dev/workflow files before committing
Verify unit/integration tests pass and note testing in the PR body

Example Use Cases

Feature: Add user authentication flow
Feature: Dashboard analytics widget
Refactor: Payment processing module for better testability
Bugfix: Fix null pointer in user profile load
API: Add v2 search endpoint with partial results handling

Frequently Asked Questions

Add this skill to your agents